Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 62D63200D16 for ; Tue, 10 Oct 2017 13:30:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 613531609E5; Tue, 10 Oct 2017 11:30:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id A6425160BE0 for ; Tue, 10 Oct 2017 13:30:03 +0200 (CEST) Received: (qmail 62027 invoked by uid 500); 10 Oct 2017 11:30:02 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 62018 invoked by uid 99); 10 Oct 2017 11:30:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Oct 2017 11:30:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 2DA4B1A5216 for ; Tue, 10 Oct 2017 11:30:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id e0w582AertsK for ; Tue, 10 Oct 2017 11:30:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 2CBEB60F18 for ; Tue, 10 Oct 2017 11:30:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 66237E0059 for ; Tue, 10 Oct 2017 11:30:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1F87824384 for ; Tue, 10 Oct 2017 11:30:00 +0000 (UTC) Date: Tue, 10 Oct 2017 11:30:00 +0000 (UTC) From: "Alexey Goncharuk (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (IGNITE-6587) Ignite watchdog service MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 10 Oct 2017 11:30:04 -0000 Alexey Goncharuk created IGNITE-6587: ---------------------------------------- Summary: 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 Fix For: 2.4 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: All TCP discovery threads All communication NIO threads (acceptor and workers) Exchange worker Striped pool threads Timeout Worker Checkpointer WAL archiver The mechanism should support pluggable components so that self-check can be extended via plugins. -- This message was sent by Atlassian JIRA (v6.4.14#64029)