They both run in one machine and the other IS node in a different machine. On Wed, Aug 7, 2013 at 11:25 AM, Sameera Jayasoma <[email protected]> wrote:
> Chamara, you've put the same hostname to ELB as well as to the IS node 1. > Is that intentional? > > Thanks, > Sameera. > > > On Wed, Aug 7, 2013 at 11:11 AM, Sameera Jayasoma <[email protected]>wrote: > >> From the logs, I can say that the second IS node is not joined the >> cluster properly. If it joins the cluster properly, you should see a log >> similar to the following. >> >> *[2013-08-07 04:51:24,933] INFO - MemberUtils Added member: >> Host:192.168.17.20, Remote Host:null, Port: 4001, HTTP:9764, HTTPS:9444, >> Domain: wso2.identity.domain, Sub-domain:mgt, Active:true* >> *[2013-08-07 04:51:24,934] INFO - HazelcastGroupManagementAgent >> Application member Host:192.168.17.20, Remote Host:null, Port: 4001, >> HTTP:9764, HTTPS:9444, Domain: wso2.identity.domain, Sub-domain:mgt, >> Active:true joined application cluster* >> * >> * >> >> >> >> On Wed, Aug 7, 2013 at 11:00 AM, Chamara Ariyarathne >> <[email protected]>wrote: >> >>> Here having a setup with One ELB and Two IS nodes (As Mgt nodes). >>> >>> When one IS node starts up; the log in the ELB >>> >>> [2013-08-07 04:51:21,806] INFO - HazelcastGroupManagementAgent Member >>> joined [e7792e38-54a7-4212-9d19-de25dbb7afd9]: /192.168.17.20:4001 >>> [2013-08-07 04:51:21,806] INFO - HazelcastGroupManagementAgent Member >>> joined [e7792e38-54a7-4212-9d19-de25dbb7afd9]: /192.168.17.20:4001 >>> [2013-08-07 04:51:24,933] INFO - MemberUtils Added member: >>> Host:192.168.17.20, Remote Host:null, Port: 4001, HTTP:9764, HTTPS:9444, >>> Domain: wso2.identity.domain, Sub-domain:mgt, Active:true >>> [2013-08-07 04:51:24,934] INFO - HazelcastGroupManagementAgent >>> Application member Host:192.168.17.20, Remote Host:null, Port: 4001, >>> HTTP:9764, HTTPS:9444, Domain: wso2.identity.domain, Sub-domain:mgt, >>> Active:true joined application cluster >>> [2013-08-07 04:51:32,112] INFO - TimeoutHandler This engine will expire >>> all callbacks after : 86400 seconds, irrespective of the timeout action, >>> after the specified or optional timeout >>> >>> So that this member joined. After that when the next IS node starts up. >>> >>> [2013-08-07 04:53:07,524] INFO - HazelcastGroupManagementAgent Member >>> joined [882bca71-8802-44f4-89ee-ebe6334e42b1]: /192.168.17.19:4002 >>> [2013-08-07 04:53:07,524] INFO - HazelcastGroupManagementAgent Member >>> joined [882bca71-8802-44f4-89ee-ebe6334e42b1]: /192.168.17.19:4002 >>> >>> So not sure if this one really joined. But after shutting down the first >>> IS node; >>> >>> [2013-08-07 04:53:38,782] INFO - HazelcastGroupManagementAgent Member >>> left [e7792e38-54a7-4212-9d19-de25dbb7afd9]: /192.168.17.20:4001 >>> [2013-08-07 04:53:38,782] INFO - HazelcastGroupManagementAgent Member >>> left [e7792e38-54a7-4212-9d19-de25dbb7afd9]: /192.168.17.20:4001 >>> [2013-08-07 04:53:43,252] INFO - HazelcastGroupManagementAgent >>> Application member Host:192.168.17.19, Remote Host:null, Port: 4002, >>> HTTP:9764, HTTPS:9444, Domain: wso2.identity.domain, Sub-domain:mgt, >>> Active:true joined application cluster >>> >>> Now the second node have joined. So now if I startup the first node >>> again; >>> >>> [2013-08-07 04:54:48,456] INFO - HazelcastGroupManagementAgent Member >>> joined [99dad4be-b2f1-4c43-a862-3b4c7b1dfb51]: /192.168.17.20:4001 >>> [2013-08-07 04:54:48,456] INFO - HazelcastGroupManagementAgent Member >>> joined [99dad4be-b2f1-4c43-a862-3b4c7b1dfb51]: /192.168.17.20:4001 >>> >>> >>> It seems that at a given time only one IS node can join. >>> >>> (Configurations attached.) >>> >>> >>> >>> -- >>> *Chamara Ariyarathne* >>> Senior Software Engineer - QA; >>> WSO2 Inc; http://www.wso2.com/. >>> Mobile; *+94772786766* >>> >> >> >> >> -- >> Sameera Jayasoma, >> Architect, >> >> WSO2, Inc. (http://wso2.com) >> email: [email protected] >> blog: http://sameera.adahas.org >> twitter: https://twitter.com/sameerajayasoma >> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections >> >> Lean . Enterprise . Middleware >> > > > > -- > Sameera Jayasoma, > Architect, > > WSO2, Inc. (http://wso2.com) > email: [email protected] > blog: http://sameera.adahas.org > twitter: https://twitter.com/sameerajayasoma > flickr: http://www.flickr.com/photos/sameera-jayasoma/collections > > Lean . Enterprise . Middleware > -- *Chamara Ariyarathne* Senior Software Engineer - QA; WSO2 Inc; http://www.wso2.com/. Mobile; *+94772786766*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
