You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Kamlesh Joshi <Ka...@ril.com> on 2020/01/31 06:42:37 UTC

exposing Ignite cluster health status in microservices

Hi Team,

Is there any sophisticated way to check if Ignite cluster is Up and Running (from spring-boot) ? Based on which, we need to keep restarting all the clients (connecting from kubernetes i.e. pod) unless and until Ignite cluster is responding properly.

Any pointers on this is appreciated !

Thanks and Regards,
Kamlesh Joshi

"Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s). 
are confidential and may be privileged. If you are not the intended recipient. you are hereby notified that any 
review. re-transmission. conversion to hard copy. copying. circulation or other use of this message and any attachments is 
strictly prohibited. If you are not the intended recipient. please notify the sender immediately by return email. 
and delete this message and any attachments from your system.

Virus Warning: Although the company has taken reasonable precautions to ensure no viruses are present in this email. 
The company cannot accept responsibility for any loss or damage arising from the use of this email or attachment."

Re: exposing Ignite cluster health status in microservices

Posted by Ilya Kasnacheev <il...@gmail.com>.
Hello!

I think you can use either JMX beans or lifecycle listener.

How to act on either one, depends on your use case.

Regards,
-- 
Ilya Kasnacheev


пт, 31 янв. 2020 г. в 09:43, Kamlesh Joshi <Ka...@ril.com>:

> Hi Team,
>
>
>
> Is there any sophisticated way to check if Ignite cluster is Up and
> Running (from spring-boot) ? Based on which, we need to keep restarting all
> the clients (connecting from kubernetes i.e. pod) unless and until Ignite
> cluster is responding properly.
>
>
>
> Any pointers on this is appreciated !
>
>
>
> *Thanks and Regards,*
>
> *Kamlesh Joshi*
>
>
>
>
> "*Confidentiality Warning*: This message and any attachments are intended
> only for the use of the intended recipient(s), are confidential and may be
> privileged. If you are not the intended recipient, you are hereby notified
> that any review, re-transmission, conversion to hard copy, copying,
> circulation or other use of this message and any attachments is strictly
> prohibited. If you are not the intended recipient, please notify the sender
> immediately by return email and delete this message and any attachments
> from your system.
>
> *Virus Warning:* Although the company has taken reasonable precautions to
> ensure no viruses are present in this email. The company cannot accept
> responsibility for any loss or damage arising from the use of this email or
> attachment."
>