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.. :(
> To get this working, ELB also should have a WK member (can be the ESB mgt
> node) and workers should have both ELB and MGT node as WK members.
>
> AFAIK QA team is aware of this. If you want, talk to IsuruW.
>
>
> On Thu, Nov 14, 2013 at 9:40 AM, Dushan Abeyruwan <[email protected]> wrote:
>
>> $subject,
>> when ELB shutdown and restarts and expecting Mgt's and Wrk's to be
>> rejoined ASAP but seems this not happening(some time it takes while to
>> join,or never joins),but when mgrs's and wrks restarts those will be
>> joining back
>>
>> FYI : QA team please do verify this..
>>
>> Cheers,
>> Dushan Abeyruwan
>> Associate Tech Lead
>> *Integration Technologies Team*
>> *WSO2 Inc. http://wso2.com/ <http://wso2.com/>*
>> *Mobile:(+94)714408632 <%28%2B94%29714408632>*
>>
>> _______________________________________________
>> Dev mailing list
>> [email protected]
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Amila Maharachchi*
> Senior Technical Lead
> WSO2, Inc.; http://wso2.com
>
> Blog: http://maharachchi.blogspot.com
> Mobile: +94719371446
>
>
--
Dushan Abeyruwan
Associate Tech Lead
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/ <http://wso2.com/>*
*Mobile:(+94)714408632*
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
