In the Siddhi case its take some time at times when using in distributed set-up.
And there use to be logs like [192.168.1.4]:5702 [siddhi5-cluster-1374770850615] ** setting master address to Address[192.168.1.4]:5701 [192.168.1.4]:5702 [siddhi5-cluster-1374770850615] ** setting master address to Address[192.168.1.4]:5701 [192.168.1.4]:5702 [siddhi5-cluster-1374770850615] ** setting master address to Address[192.168.1.4]:5701 [192.168.1.4]:5702 [siddhi5-cluster-1374770850615] ** setting master address to Address[192.168.1.4]:5701 [192.168.1.4]:5702 [siddhi5-cluster-1374770850615] ** setting master address to Address[192.168.1.4]:5701 [192.168.1.4]:5702 [siddhi5-cluster-1374770850615] ** setting master address to Address[192.168.1.4]:5701 [192.168.1.4]:5702 [siddhi5-cluster-1374770850615] ** setting master address to Address[192.168.1.4]:5701 printed continuously But I'm not sure whether these are the same issue. Suho On Thu, Jul 25, 2013 at 7:58 PM, Afkham Azeez <[email protected]> wrote: > This is the time it takes for Hazelcast to initialize. We will have to dig > into the Hazelcast code to see why it takes so long. > > Suho, when you guys were using Hazelcast, did you notice such delays as > well? > > > On Thu, Jul 25, 2013 at 12:21 PM, Nirodha Pramod <[email protected]> wrote: > >> >> >> >> On Thu, Jul 25, 2013 at 12:01 PM, Nirodha Pramod <[email protected]>wrote: >> >>> Hi, >>> >>> You can see the below logs, when multicast clustering is enabled, it >>> takes around 1 minute to do the cluster initialization. >>> >>> [2013-07-25 11:54:50,339] INFO >>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} - HTTPS port >>> : 9443 >>> [2013-07-25 11:54:50,339] INFO >>> {org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP port >>> : 9763 >>> [2013-07-25 11:54:50,361] INFO >>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} - >>> Cluster domain: qa.420.com >>> *[2013-07-25 11:54:50,361]* INFO >>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} - >>> Using multicast based membership management scheme >>> >>> *2013-07-25 11:55:53,924]* INFO >>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} - >>> Local member: [16c42b2b-79c8-4832-a0dc-c8d331f7ea26] - Host:localhost, >>> Remote Host:null, Port: 4000, HTTP:9763, HTTPS:9443, Domain: qa.420.com, >>> Sub-domain:worker, Active:true >>> [2013-07-25 11:55:54,050] INFO >>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} - >>> Cluster initialization completed >>> >>> >>> regards, >>> Nirodha >>> >>> -- >>> * >>> * >>> *Nirodha Gallage* >>> Senior Software Engineer, QA. >>> WSO2 Inc.: http://wso2.com/ >>> Mobile: +94716429078 >>> >> >> >> >> -- >> * >> * >> *Nirodha Gallage* >> Senior Software Engineer, QA. >> WSO2 Inc.: http://wso2.com/ >> Mobile: +94716429078 >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Afkham Azeez* > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > * <http://www.apache.org/>** > email: **[email protected]* <[email protected]>* cell: +94 77 3320919 > blog: **http://blog.afkham.org* <http://blog.afkham.org>* > twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> > * > linked-in: **http://lk.linkedin.com/in/afkhamazeez* > * > * > *Lean . Enterprise . Middleware* > -- *S. Suhothayan * Associate Technical Lead, *WSO2 Inc. *http://wso2.com * <http://wso2.com/>* lean . enterprise . middleware *cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/ twitter: http://twitter.com/suhothayan | linked-in: http://lk.linkedin.com/in/suhothayan* * *
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
