From dev-return-32054-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Thu Mar 15 02:13:33 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 744C6180654 for ; Thu, 15 Mar 2018 02:13:32 +0100 (CET) Received: (qmail 21328 invoked by uid 500); 15 Mar 2018 01:13:31 -0000 Mailing-List: contact dev-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 dev@ignite.apache.org Received: (qmail 21317 invoked by uid 99); 15 Mar 2018 01:13:31 -0000 Received: from mail-relay.apache.org (HELO mailrelay2-lw-us.apache.org) (207.244.88.137) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Mar 2018 01:13:31 +0000 Received: from mail-it0-f51.google.com (mail-it0-f51.google.com [209.85.214.51]) by mailrelay2-lw-us.apache.org (ASF Mail Server at mailrelay2-lw-us.apache.org) with ESMTPSA id 448D81AC9 for ; Thu, 15 Mar 2018 01:13:30 +0000 (UTC) Received: by mail-it0-f51.google.com with SMTP id k135-v6so6975494ite.2 for ; Wed, 14 Mar 2018 18:13:30 -0700 (PDT) X-Gm-Message-State: AElRT7FQEkJQD9BJQ8pv5/o+SXhfGEvyEllohVtJver+9LnNIeiLy0NP QeHVBzhSkgvT1H/gZyBsOsCfQDYMw7GvuGrNU7BWnQ== X-Google-Smtp-Source: AG47ELsWb6DwrmV3AT4Bi7ypR57xzhtx0YAP3zFebFQg+jez5M1+NkE+gXX0olJRZj6sKkneKKMLAmwq0emFnTDcoSk= X-Received: by 2002:a24:9e8b:: with SMTP id p133-v6mr4541815itd.143.1521076409581; Wed, 14 Mar 2018 18:13:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.2.25.69 with HTTP; Wed, 14 Mar 2018 18:12:49 -0700 (PDT) In-Reply-To: References: <19ee9ce1-1790-a28a-72bb-74441656d255@gmail.com> <49d04ab7-c701-05f3-7572-1030fd3b96a2@gmail.com> From: Dmitriy Setrakyan Date: Wed, 14 Mar 2018 21:12:49 -0400 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: IEP-14: Ignite failures handling (Discussion) To: dev@ignite.apache.org Content-Type: multipart/alternative; boundary="00000000000011fb6a0567693354" --00000000000011fb6a0567693354 Content-Type: text/plain; charset="UTF-8" On Tue, Mar 13, 2018 at 11:17 PM, Nick Pordash wrote: > I can tell you as a user that if any library I was using in my application > called System.exit without my consent would result in a lot of frustration. > > If ignite enters an unrecoverable state then I think that is something that > should be observable locally, similar to node segmentation and then the > application can decide the best course of action. > Nick, you would be a lot more frustrated if Ignite was frozen and every call to Ignite would freeze the application threads as well. Again, if you prefer to keep the process around, even if Ignite freezes, then you can always configure this behavior, but I still believe that the default should be to kill the process. Ignite is a horizontally scalable system, so killing of one node should not be a significant event and should not disrupt the cluster. However, a freeze of one node is a significant event and can bring the whole cluster to a halt. D. --00000000000011fb6a0567693354--