You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Goncharuk (JIRA)" <ji...@apache.org> on 2018/04/09 14:06:00 UTC
[jira] [Updated] (IGNITE-6587) Ignite watchdog service
[ https://issues.apache.org/jira/browse/IGNITE-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Goncharuk updated IGNITE-6587:
-------------------------------------
Fix Version/s: (was: 2.6)
2.5
> Ignite watchdog service
> -----------------------
>
> Key: IGNITE-6587
> URL: https://issues.apache.org/jira/browse/IGNITE-6587
> Project: Ignite
> Issue Type: Improvement
> Components: general
> Affects Versions: 2.2
> Reporter: Alexey Goncharuk
> Priority: Major
> Labels: IEP-5
> Fix For: 2.5
>
> Attachments: watchdog.sh
>
>
> We need to come up with a 'watchdog service' to monitor for Ignite node local health and kill the process under some critical conditions.
> For example, if one of the mission-critical Ignite threads die, the Ignite node must be stopped.
> At the first glance, the list of critical threads is:
> disco-event-worker
> tcp-disco-sock-reader
> tcp-disco-srvr
> tcp-disco-msg-worker
> tcp-comm-worker
> grid-nio-worker-tcp-comm
> exchange-worker
> sys-stripe
> grid-timeout-worker
> db-checkpoint-thread
> wal-file-archiver
> ttl-cleanup-worker
> nio-acceptor
> The mechanism should support pluggable components so that self-check can be extended via plugins.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)