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 62116200BF3 for ; Thu, 22 Dec 2016 02:32:39 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 60915160B39; Thu, 22 Dec 2016 01:32:39 +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 A78DC160B26 for ; Thu, 22 Dec 2016 02:32:38 +0100 (CET) Received: (qmail 15632 invoked by uid 500); 22 Dec 2016 01:32:32 -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 15617 invoked by uid 99); 22 Dec 2016 01:32:32 -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; Thu, 22 Dec 2016 01:32:32 +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 54C061AA1FA for ; Thu, 22 Dec 2016 01:32:32 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.399 X-Spam-Level: ** X-Spam-Status: No, score=2.399 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_H2=-0.001, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd2-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 (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 7GbdsikInwXR for ; Thu, 22 Dec 2016 01:32:31 +0000 (UTC) Received: from mail-io0-f173.google.com (mail-io0-f173.google.com [209.85.223.173]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 7C56E5F474 for ; Thu, 22 Dec 2016 01:32:30 +0000 (UTC) Received: by mail-io0-f173.google.com with SMTP id m133so35246151iom.3 for ; Wed, 21 Dec 2016 17:32:30 -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=1JzpSV/9xBm0e/E0vortaMIDj25kYrjqwigqgbnHs4M=; b=NwHh7ABjVJ6RsBoTNuavMJgCNiN/PuUodnW3tDuq6V4vrg5R/DQXt1pRmfhcQe2WWc qiVJo5g+4bYfwJT7ARscQo9w4drVWh2r67Aek2UBlzQkH8r6ZoOPPUH/o7XYq9qtl3EN mICeAs0CkHMNM5dxHnxtQCDUkzHm9FqMggvv4a6SmAaGQXU2kCc6RhMeAh8AFxiGjPEd gEuU4vCQwrj/BqF9+Ra9iFxpp77zAlvEaeVqTVB8hTRSevF1cmEG96VyEZ6Ou5qok6bG KsvjTttgGhZtOd+MpCiJ7TIHQMuhDW3lekOgu6FYAe+6hMTJ6Mkv+x9nvjHkcq7I9wh8 p1DA== 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=1JzpSV/9xBm0e/E0vortaMIDj25kYrjqwigqgbnHs4M=; b=FEp6oOGogGZvXYjZ+U8Dm7cCnuyQk9fDeQCIQQB72qMvbbhnMvm5412aRjaCGGLQIK VbCVIl66idyiJvc2F8frngPxLElO1ItwJ4Ens3pJVMcvkjCKGxbfn8MjrRJhLnXnswat Gfh/723olksq7+SNcDJ5js4RjPzlzbUrKbDe+W31rv00mFkTWCyvO3OzQ8k2L0henkVN fybz+2Wjgn65cytabKLqYzipKKBbVGxfqYwP9yxw9aDntbINjuKulj/0cTohTavh44Zf ax5SD3ke4NLof182rk9pAGNEj3+tsziLazl24qolBi0nyU/Qf+odu1zy480fU7N58n99 g12g== X-Gm-Message-State: AIkVDXJj8Uvzp051kU0hEOKYc87LTPO3JaxbQ1ueiubfSYbVd8iSNDqdRlSFs5vg3n4r7W9BoveUTJznvyDHzA== X-Received: by 10.107.34.74 with SMTP id i71mr9165305ioi.24.1482370349299; Wed, 21 Dec 2016 17:32:29 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.189.66 with HTTP; Wed, 21 Dec 2016 17:31:48 -0800 (PST) In-Reply-To: <1482346558286-9686.post@n6.nabble.com> References: <1482255674220-9649.post@n6.nabble.com> <1482346558286-9686.post@n6.nabble.com> From: Anil Date: Thu, 22 Dec 2016 07:01:48 +0530 Message-ID: Subject: Re: Ignite cluster To: user@ignite.apache.org Content-Type: multipart/alternative; boundary=001a1140f254187e940544353e90 archived-at: Thu, 22 Dec 2016 01:32:39 -0000 --001a1140f254187e940544353e90 Content-Type: text/plain; charset=UTF-8 Hi Val, I agree with you on "separate clusters running". but ignite is stopped. Separate clusters has no meaning. agree? Thanks On 22 December 2016 at 00:25, vkulichenko wrote: > Anil, > > All this is very use case specific. STOP is used by default because it's > the > safest option and gives more control. However, it does imply some manual > operations to resolve the segmentation. > > In any case, above is about the feature that is available only in GridGain, > not in Ignite. In Ignite you will just have two separate clusters running, > which sounds like the behavior you're looking for. > > -Val > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Ignite-cluster-tp9527p9686.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > --001a1140f254187e940544353e90 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Val,

I agree with you on "separ= ate clusters running". but ignite is stopped. Separate clusters has no= meaning. agree?

Thanks

On 22 December 2016 at 00:25, vk= ulichenko <valentin.kulichenko@gmail.com> wrote:=
Anil,

All this is very use case specific. STOP is used by default because it'= s the
safest option and gives more control. However, it does imply some manual operations to resolve the segmentation.

In any case, above is about the feature that is available only in GridGain,=
not in Ignite. In Ignite you will just have two separate clusters running,<= br> which sounds like the behavior you're looking for.

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-clu= ster-tp9527p9686.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

--001a1140f254187e940544353e90--