hazelcast shutdown

432 views
Skip to first unread message

Adil C.

unread,
Jun 15, 2015, 11:01:11 AM6/15/15
to haze...@googlegroups.com
Hi guys,

Is that correct that when a HZ node can't communicate with the others nodes causes tomcat shutdown??

i don't think so but the systems engineers said that.

i have another question, what is the goal of setting this property:  hazelcast.shutdownhook.enabled

thanks

Hasan Çelik

unread,
Jun 16, 2015, 8:20:00 AM6/16/15
to haze...@googlegroups.com
Hi Adil,

If you meant that when you shutdown tomcat server , can its hazelcast nodes communicate with other tomcat's hazelcast nodes ? ,Answer is they can not communicate with each other , because tomcat kills all its operations.

For the second question from our documentation:

Enable Hazelcast shutdownhook thread. When this is enabled, this thread terminates the Hazelcast instance without waiting to shutdown gracefully.

sparking...

unread,
Jun 16, 2015, 10:00:09 AM6/16/15
to haze...@googlegroups.com
no, my question was that if a HZ node can't communicate with tomcat's hz nodes CAN CAUSE tomcat shutdown for some reason?

Daniel López

unread,
Jun 16, 2015, 10:19:17 AM6/16/15
to haze...@googlegroups.com
If you make HZ communication part of the startup process and failing to communicate raises an exception, it can cause the Tomcat not to startup properly and die/shutdown. That, I have seen.

But once it is up & running, I've never seen Hazelcast causing a shutdown, it makes no sense.

--
You received this message because you are subscribed to the Google Groups "Hazelcast" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hazelcast+...@googlegroups.com.
To post to this group, send email to haze...@googlegroups.com.
Visit this group at http://groups.google.com/group/hazelcast.
To view this discussion on the web visit https://groups.google.com/d/msgid/hazelcast/b29d7b96-d349-4259-9cef-6c3af7f95b5c%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

sparking...

unread,
Jun 16, 2015, 11:41:34 AM6/16/15
to haze...@googlegroups.com
that was my guess even if the system engineers continues to affirm that's caused by hz communication problems

thanks

Sertuğ Kaya

unread,
Jun 17, 2015, 8:21:33 AM6/17/15
to haze...@googlegroups.com
Hi;
It will be better if your system engineer can share the shutdown logs about this issue.
About the shutdown hook here's my 2 cents;
In general, shutdown hooks are basically used to registering a thread to be started right before the VM shuts down. This thread usually can include cleanup operations, logging etc. 
In Hazelcast, shutdown hook is triggered when JVM is shutting down externally (e.g. pressing ctrl+c from terminal while an instance is running). Orderly shutdowns do not need the hook.
Regards.
Reply all
Reply to author
Forward
0 new messages