Here is the response I got from the Hazelcast forum. The startup delay you experience should be there only for the very first node in the cluster. Please confirm that this delay was seen only for the very first node.
--------------------------------------------------- Yes, it's by design. MulticastTimeoutSeconds defines the time that a node should wait for a valid multicast response from another node running in the network before declaring itself as master node and creating its own cluster. This applies to only the first node, other nodes should get a reply from the first in a short time and join to it. @mmdogan On Fri, Jul 26, 2013 at 12:25 PM, Afkham Azeez <[email protected]> wrote: > Hi, > > > I set the multicast timeout using the following method; > > MulticastConfig#setMulticastTimeoutSeconds > > Then I create a Hazelcast instance as follows: > Hazelcast.newHazelcastInstance(primaryHazelcastConfig) > > > I noticed that the time it takes for the new Hazelcast instance creation > is proportional to the time I set in the setMulticastTimeoutSeconds. For > example, if I set the timeout to 60s, Hazelcast instance creation takes > about 63s, and so on. > > Is this by design? How is the timeout related to Hazelcast instance > creation time? > > Thanks > Azeez > On Fri, Jul 26, 2013 at 2:57 PM, Afkham Azeez <[email protected]> wrote: > I looked into this, and narrowed the problem down to the mcast timeout > value. For some reason, Hazelcast instance creation increases with an > increased mcast timeout value. I have raised this on the Hazelcast forum. > > Azeez > > > 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* >> > > > > -- > *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* > -- *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*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
