client calls select first available server, rather than hashing with the unique id

Bug #1481993 reported by Clint Byrum on 2015-08-06
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Gearman
Wishlist
Unassigned

Bug Description

Seems like a huge oversight. The gearman protocol gives you all the tools to use resilient stable hash rings to minimize the impact of failed servers, and yet libgearman just chooses the first working server to submit all of its jobs to.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers