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.
Hi Azeez,
Yes this happens only in the first node of the cluster. Basically when
other nodes of the cluster are not started yet, then the first node waits
for other nodes to initialize the cluster. And as you pointed out that time
can be configured by changing,
parameter
But I think it is fine for the very first node in the cluster to take some
time to startup.
Azeez
On Fri, Jul 26, 2013 at 6:00 PM, Nirodha Pramod niro...@wso2.com wrote:
Hi Azeez,
Yes this happens only in the first node of the cluster. Basically when
other nodes of the cluster are not
Yes, I too think it's fine to for the very first node, and since that
waiting time is configurable it is ok.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
On Thu, Jul 25, 2013 at 12:01 PM, Nirodha Pramod niro...@wso2.com 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
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 niro...@wso2.com wrote:
On Thu, Jul
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
