Well, it is exactly the same situation as any other situation where connection to another server fails. There is no need to insert a delay here unless you think that there should be a delay before this particular warning should be considered a warning.
Would you like to suggest a patch? On Wed, Aug 17, 2011 at 8:40 PM, Sampath Perera <[email protected]>wrote: > So my question is whether it is possible to configure an initial delay for > the FastLeaderElection to be kicked off? > > The rationale being that it is highly unlikely that all 3 nodes started at > the same time, even in the case where we try to command the startups at the > same time, and we could get rid of this stacktrace from the logs, as this > will trigger warning on the tools that are monitoring the logs, yet is not > actually a WARN rather an expected error. >
