On Thu, Nov 14, 2013 at 9:55 AM, Dushan Abeyruwan <[email protected]> wrote:
> > > > On Thu, Nov 14, 2013 at 9:50 AM, Amila Maha Arachchi <[email protected]>wrote: > >> You need to have at least one WK member in a given time when you are >> dealing with hazelcast. If ELB is the only WK member in your setup, when >> you restart the ELB, others will never join the ELB until they are >> restarted. >> > > Is this kind of a norm .. a hard fasten rule we have seutp with the > newst WK implementation. ? Wonder I should agree on this or not..assume > there is a pool which as larger number of wrks..and Do i need to restart > them all? Is that what you trying to emphasis.. > > l.e assume my prod set has only 1 ELB and 30 works.. :)... so I need to > start all 30 if ELB goes down ...woops.. :( > Please slow down a bit when typing mail & sending them, and read through it once, so that others clearly get your message. You seemed to be getting over excited :) One WK member in a setup is not a recommended approach anyway, since that WKA member will will become the single point of failure. Hazelcast assumes that at least one static (WK) member exists at any given time. So, you will need at least two static members to ensure that cluster membership always works correctly. However, if both those static members fail at the same time, again the whole cluster is affected. To reduce the possibility of this happening, we have to increase the number of static members. Anyway, this is something that I am planning to take up during the Hazelcast consultancy next month.
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
