Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: <CABDss3hf0mv6vo9tv2Oc=uNgZrs-UWLPJnH99HD=s70hYT+6ew@mail.gmail.com>
References: <CAHKVN8gHrFcRZDSp+ZbQ_GJbY1AZ4ajRAUasvpGjjWzd5YhhKQ@mail.gmail.com>
 <DEC4CB83-C883-4B18-BAB2-375522B0A8EB@apache.org> <CABDss3hf0mv6vo9tv2Oc=uNgZrs-UWLPJnH99HD=s70hYT+6ew@mail.gmail.com>
From: Yakov Zhdanov <yzhdanov@apache.org>
Date: Thu, 3 Aug 2017 12:15:24 +0300
Message-ID: <CAGcMBHh9cdj-2uOrCkUYSsGDRddk7gigz_Xu7YTbwSSxj6FJDA@mail.gmail.com>
Subject: Re: Cluster auto activation design proposal
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary="94eb2c1cd06a26e8a60555d5d2e0"
archived-at: Thu, 03 Aug 2017 09:15:29 -0000

--94eb2c1cd06a26e8a60555d5d2e0
Content-Type: text/plain; charset="UTF-8"

> * Based on some sort of policies when the actual cluster topology differs
too much from the baseline or when some critical condition happens (e.g.,
when there are no more backups for a partition)

Good point, Alex! I would even go further. If cluster is active and under
load and nodes continue joining and leaving then we can have several BT's
that are possible to restart on - the main condition is to have all the up
to date data partitions. I.e. if you have 4 servers and 3 backups most
probably you can have all the data with 2, 3 and, of course, 4 nodes. Makes
sense?

I would also think of different name. Topology (for me) also implies the
version, but here only nodes carrying data are important. How about
"restart nodes set"?

--Yakov

--94eb2c1cd06a26e8a60555d5d2e0--