Am 24.09.15 um 10:45 schrieb Stefan Egli: > Hi, > > There are various options here: you could distribute the 'queue chiefs' > via some hashing amongst all instances in the cluster view, and reassign > those chiefs upon a topology change. Or you could let the leader > explicitly send a 'become-chief' job/command to particular instances that > would then blush and proudly start as chief of a particular queue - and a > 'step-down-as-chief' command in case the leader detects it needs to > redistribute load. >
Right, I guess a hash based selection is easier as it avoids any additional communication which then might require acks and so on. Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
