Re: [jira] [Created] (CURATOR-44) LeaderSelector does not assign leader randomly

[Eric Tschetter <ec...@gmail.com>]

I'm not quite sure I fully understand the use case, but if you are counting
on randomness to create an even distribution of leaders across your nodes,
it seems like having the application choose to "give up" leadership either
periodically or based on having "too many" tasks that it is in charge of.

It would be pretty difficult to figure out how to correctly interrupt the
current leader at the correct time from Curator, but it should be pretty
simple for the application itself to know when a good time is.

Re: [jira] [Created] (CURATOR-44) LeaderSelector does not assign leader randomly

[Jay Zarfoss <jz...@netflix.com>]

> it seems like having the application choose to "give up" leadership either
periodically or based on having "too many" tasks that it is in charge of.

Agreed that definitely smells better.  So sounds like this issue is just a
javadoc update.



On Thu, Jul 18, 2013 at 7:12 PM, Eric Tschetter <ec...@gmail.com> wrote:

> I'm not quite sure I fully understand the use case, but if you are counting
> on randomness to create an even distribution of leaders across your nodes,
> it seems like having the application choose to "give up" leadership either
> periodically or based on having "too many" tasks that it is in charge of.
>
> It would be pretty difficult to figure out how to correctly interrupt the
> current leader at the correct time from Curator, but it should be pretty
> simple for the application itself to know when a good time is.
>