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 7780C200BD4 for ; Fri, 16 Dec 2016 11:21:31 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 76442160B24; Fri, 16 Dec 2016 10:21:31 +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 99496160AF6 for ; Fri, 16 Dec 2016 11:21:30 +0100 (CET) Received: (qmail 23552 invoked by uid 500); 16 Dec 2016 10:21:29 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 23542 invoked by uid 99); 16 Dec 2016 10:21:29 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Dec 2016 10:21:29 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 259E0C00E7 for ; Fri, 16 Dec 2016 10:21:29 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.879 X-Spam-Level: * X-Spam-Status: No, score=1.879 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id B9pEh4rT5Mhr for ; Fri, 16 Dec 2016 10:21:27 +0000 (UTC) Received: from mail-oi0-f51.google.com (mail-oi0-f51.google.com [209.85.218.51]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 5E0FC5F54E for ; Fri, 16 Dec 2016 10:21:27 +0000 (UTC) Received: by mail-oi0-f51.google.com with SMTP id v84so73216015oie.3 for ; Fri, 16 Dec 2016 02:21:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=rbJymuUIi5dnOGxaMtiSg8l6rHA6E2Fn9KnKhIu9YRY=; b=adnH6zm974rPYt1FeVGqisNu1raj6qVKOdMdCv9Q7ZRBiAR57Qj4pbqaY+hvPvYgYM z8OOfmDNMyUhhbwMLmrBYDxmfRCgt17Atp9GMl61rKxw5rYpgTES8X67aoVc9bdEW60D wI04gC6gKSk52AEYRqLRz0fyaXG0vKzXrzN1SDjhHlP+2XHO7+5skyy+kOy8zrgtfXaN uN5hrfyQH8b5TbE6jIk9PLgLg6pq6ilBH17kjh7N0PM0AEmQ7lyKqmwrUJBJQONvAAlW 9gANoPh9JdKX1ws9kmsuQ2fBP9+AYNz9vElq12LksX7XTES2ZddFJSRPxx4sVMUA8GFh uLYg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=rbJymuUIi5dnOGxaMtiSg8l6rHA6E2Fn9KnKhIu9YRY=; b=fnF5HhiU7NBpAChGHQwncLmIi28lgYaiGzxqC/qi2Cdr1VbE9+HPVY6nrTT4fPk2u/ GmJp08vxdMra4jCTPVBn+Bs8NjaBe4sC7uOEKnzJqL0Shs5rMZ24kMltL61TDektiuOg Z6Ky064dM2vtQcegzW/7YXumFoRLGvjibSTiUSfpfLnmwqyIvrQFCAv0RLRSwhVimybU bn5x0f4Sdg1XMZee9u7F+K2FlTuuK/+8oQwUlIErUocPa1iODQhT14YAjSUN1wWYrvCV WW1kaPy9ioMfM6/66OClCtdDaKcn5kBw1oGXI8lE2DsxyTdsXDgBDcBtHKhXveoFYWDY Jo3g== X-Gm-Message-State: AIkVDXKGcHBFUWehFIjE3qb0vh9Fl/KZAtjsI9UQayfTKXWGWybbWOQ9GJgyFOXRxCcM8dm7zkeT9Us09jOzHQ== X-Received: by 10.202.173.82 with SMTP id w79mr1399360oie.134.1481883686078; Fri, 16 Dec 2016 02:21:26 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.5.5 with HTTP; Fri, 16 Dec 2016 02:21:25 -0800 (PST) In-Reply-To: References: <1481635766479-9509.post@n6.nabble.com> From: Alexandr Kuramshin Date: Fri, 16 Dec 2016 17:21:25 +0700 Message-ID: Subject: Re: Cache stopped To: user@ignite.apache.org Content-Type: multipart/alternative; boundary=001a113ceca2b50c250543c3eeeb archived-at: Fri, 16 Dec 2016 10:21:31 -0000 --001a113ceca2b50c250543c3eeeb Content-Type: text/plain; charset=UTF-8 Hi Anil, Right, you get stopping the node by the cause of segmentation. Call chain: org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.DiscoveryWorker#onSegmentation org.apache.ignite.internal.managers.discovery.GridDiscoveryManager#stopNode org.apache.ignite.Ignition#stop(java.lang.String, boolean) You could change IgniteConfiguration.setSegmentationPolicy() to SegmentationPolicy.NOOP, so the node will not be stopped upon segmentation (the default value is STOP). But the better way is to deploy the kafka streamer as a node singleton [1], and implement it as a service, which could be automatically stopped right before node do. [1] http://apacheignite.gridgain.org/docs/cluster-singletons 2016-12-16 13:29 GMT+07:00 Anil : > Hi Anton and Alexandr, > > I thought vertx is invoking IgniteClusterManager#leave because of network > segmentation. so I created wrapper to IgniteClusterManager and added logs > before invoking leave(). I did not see any log of wrapper. So ignite is not > closed from the IgniteClusterManager#leave > > Looks like ignite is stopped from some where else because of network > segmentation? can you help me in understanding this. is there any to > intercept behavior ? > > In my scenario, i am starting kafka streamer when ignite is up and need > to stop the kafka streamer before closing the ignite due to any problem. > otherwise, it would lead to data problem. and i am using vertx-ignite. > > please share if there are other cluster manager better than vertx ? > > Thanks for you help. > > > - Anil > > -- Thanks, Alexandr Kuramshin --001a113ceca2b50c250543c3eeeb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi = Anil,

Right, you get stop= ping the node by the cause of segmentation.

Call chain:

org.apache.ignite.= internal.managers.discovery.GridDiscoveryManager.DiscoveryWorker#onSegmenta= tion
org.ap= ache.ignite.internal.managers.discovery.GridDiscoveryManager#stopNode
=
org.apache.ignite.Ignition#stop(java.lang.Stri= ng, boolean)

You could change=C2=A0IgniteConfiguration.setSegmentationPol= icy() to=C2=A0SegmentationPolicy.NOOP, so the node will not be stopped upon= segmentation (the default value is STOP).

But the better way is to deploy th= e kafka streamer as a node singleton [1], and implement it as a service, wh= ich could be automatically stopped right before node do.

[1]=C2=A0http://apacheigni= te.gridgain.org/docs/cluster-singletons


2016= -12-16 13:29 GMT+07:00 Anil <anilklce@gmail.com>:
Hi Ant= on and Alexandr,

I thought vertx is invoking IgniteClusterManager#leave because o= f network segmentation. so I created wrapper to IgniteClusterManager and ad= ded logs before invoking leave(). I did not see any log of wrapper. So igni= te is not closed from the IgniteClusterManager#leave

Looks like ignite is stopped= from some where else because of network segmentation? can you help me in u= nderstanding this. is there any to intercept behavior ?

In my scenario, =C2=A0i a= m starting kafka streamer when ignite is up and need to stop the kafka stre= amer before closing the ignite due to any problem. otherwise, it would lead= to data problem. and i am using vertx-ignite.=C2=A0

please share if there are ot= her cluster manager better than vertx ?
Thanks for you help.


- Anil




--
Thanks,
Alexandr Kuramshin
=
--001a113ceca2b50c250543c3eeeb--