gt; > > > > > > > >After that we shutdown that
> Part1_grid.
> > > > > > > > > > > > > > > > > >4. We start and activate Part2_grid.
> > > > Topology
> > > > > > also
>
> > > > > > > ->
> > > > > > > > > > > > > > > > BLT#3
> > > > > > > > > > > > > > > > >created.
> > > > > > > > > > > > > > > > >5. Then we start Part1_grid and it's
> nodes
> > > try
> > > > > to
> > > > > > > join
> > > > > > > > > > >
; > state
> > > of
> > > > > the
> > > > > > > > > > resulting
> > > > > > > > > > > > > grid:
> > > > > > > > > > > > > > > > values for the same key may (and will) differ
> > > > between
> > > > > > > grid
> > > > > > > > > > parts.
> > > > > > > > >
t; > > > > > > > grid
> > > > > > > > > > > > > > > with BLT#3. And we should fail nodes with an
> > error
> > > > > > message.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Thanks,
> > > > > > > > > > > > > > > Sergey.
> &g
gt; > > On Wed, Aug 23, 2017 at 5:47 AM, Dmitriy
> Setrakyan
> > <
> > > > > > > > > > > > > dsetrak...@apache.org>
> > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Sergey, I am still confused. What is the
> &g
; > > > > > > > > > > >
> > > > > > > > > > > > > > D.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On Tue, Aug 22, 2017 at 4:47 AM
erstand you use the term
> > > > "minimalActivationNodes"
> > > > > > as
> > > > > > > a
> > > > > > > > > > > synonym
> > > > > > > > > > > > > for
> > > > > &
wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Dmitriy,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > As I understand you use the term
> > > > "minimalActivationNodes"
> > > > > > as
> > > > > > > a
>
ree with you that we can replace
> > both
> > > > > > > > "establish*"
> > > > > > > > > > > > methods
> > > > > > > > > > > > > with a simple setter method (see below in summary).
> > > > > > > > > > > > >
> > > > > > > > > > > > > Summing up the whole discussion I see the
> > functionality
> > &g
ures
> > > > > > it
> > > > > > > > > > enables
> > > > > > > > > > > > are:
> > > > > > > > > > > >
> > > > > > > > > > > >1. automatic activation of cluster;
> > > > > > > > > >
t; > > > > >3. eliminating of rebalancing traffic on short-term
> > node
> > > > > > > failures.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Use cases to create BLT:
> > > > > > > > > > >
> > > > > > > > > > >1. user starts up new cluster of desired number of
> >
gt; presented
> > > > > > in
> > > > > > > > the
> > > > > > > > > >cluster at the moment of activation, no API is needed;
> > > > > > > > > >
> > > > > > > > > >2. user prepares BLT using web-console or visor CMD
> > tools
> > > > and
> > > > > > sets
> >
selin
> eTopology(BaselineTopology
> > > > blt);
> > > > > > > > >
> > > > > > > > >3. user provides via static configuration a list of
> nodes
> > > that
> > > > > are
> > > > > > > > >expected to be in the cluster.
> > > > > > > > >User starts nodes one by one; when all preconfigured
> > > > > > > Igniters, does this description match with your understanding
> > of
> > > > > > > > functionality? If it does I'll create a set of tickets and
> > start
> > > > > > working
> > > > > > > on
> > > > > > > > implementation.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Sergey.
> > > > > > > >
> > > > > > > >
> > > > > > > > On Sat, Aug 19, 2017 at 5:41 PM, Dmitriy Setrakyan <
> > > > > > > dsetrak...@apache.org>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > I still do not see why anyone would explicitly call these 2
> > > > > methods:
> > > > > > > > >
> > > > > > > > > *Ignite::activation::establishBaselineTopology();*
> > > > > > > > > *Ignite::activation::establishBaselineTopology(
> > > BaselineTopology
> > > > > > > > bltTop);*
> > > > > > > > >
> > > > > > > > > For example, if a web console, or some other admin process,
> > > want
> > > > to
> > > > > > > > > automatically set currently started nodes as the baseline
> > > > topology,
> > > > > > > > > shouldn't they just call a setter for
> minimalActivationNodes?
> > > > > > > > >
> > > > > > > > > D.
> > > > > > > > >
> > > > > > > > > On Fri, Aug 18, 2017 at 10:18 AM, Alexey Dmitriev <
> > > > > > > > admitr...@gridgain.com>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > API is proposed in the head of the thread by Sergey, as I
> > > > > > understood:
> > > > > > > > > > __
> > > > > > > > > >
> > > > > > > > > > API for BaselineTopology manipulation may look like this:
> > > > > > > > > >
> > > > > > > > > > *Ignite::activation::establishBaselineTopology();*
> > > > > > > > > > *Ignite::activation::establishBaselineTopology(
> > > BaselineTopology
> > > > > > > > > bltTop);*
> > > > > > > > > >
> > > > > > > > > > Both methods will establish BT and activate cluster once
> it
> > > is
> > > > > > > > > established.
> > > > > > > > > >
> > > > > > > > > > The first one allows user to establish BT using current
> > > > topology.
> > > > > > If
> > > > > > > > any
> > > > > > > > > > changes happen to the topology during establishing
> process,
> > > > user
> > > > > > will
> > > > > > > > be
> > > > > > > > > > notified and allowed to proceed or abort the procedure.
> > > > > > > > > >
> > > > > > > > > > Second method allows to use some monitoring'n'management
> > > tools
> > > > > like
> > > > > > > > > > WebConsole where user can prepare a list of nodes, using
> > them
> > > > > > create
> > > > > > > a
> > > > > > > > BT
> > > > > > > > > > and send to the cluster a command to finally establish
> it.
> > > > > > > > > >
> > > > > > > > > > From high level BaselineTopology entity contains only
> > > > collection
> > > > > of
> > > > > > > > > nodes:
> > > > > > > > > >
> > > > > > > > > > *BaselineTopology {*
> > > > > > > > > > * Collection nodes;*
> > > > > > > > > > *}*
> > > > > > > > > >
> > > > > > > > > > *TopologyNode* here contains information about node - its
> > > > > > consistent
> > > > > > > id
> > > > > > > > > and
> > > > > > > > > > set of user attributes used to calculate affinity
> function.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > View this message in context: http://apache-ignite-
> > > > > > > > > > developers.2346864.n4.nabble.
> com/Cluster-auto-activation-
> > > > > > > > > > design-proposal-tp20295p21066.html
> > > > > > > > > > Sent from the Apache Ignite Developers mailing list
> archive
> > > at
> > > > > > > > > Nabble.com.
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
plementation.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Sergey.
> > > > > > >
> > > > > > >
> > > > > > > On Sat, Aug 19, 2017 at 5:41 PM, Dmitriy Setrakyan <
> > > > > > dsetrak...@apache.org>
> > > > > > > wrote:
> > > > > >
> > > > > > > *Ignite::activation::establishBaselineTopology();*
> > > > > > > *Ignite::activation::establishBaselineTopology(
> BaselineTopology
> > > > > > bltTop);*
> > > > > > >
> > > > > > > For example, if a web console, or some other admin process,
> want
> > to
> &
t; topology,
> > > > > > shouldn't they just call a setter for minimalActivationNodes?
> > > > > >
> > > > > > D.
> > > > > >
> > > > > > On Fri, Aug 18, 2017 at 10:18 AM, Alexey Dmitriev <
> > > > > admitr...@gridgain.com>
> > > > > > wrote:
> &
> API is proposed in the head of the thread by Sergey, as I
> > understood:
> > > > > > __
> > > > > >
> > > > > > API for BaselineTopology manipulation may look like this:
> > &
:establishBaselineTopology(BaselineTopology
> > > > bltTop);*
> > > > >
> > > > > Both methods will establish BT and activate cluster once it is
> > > > established.
> > > > >
> > > > > The first one allows user to establish BT using current topol
g current topology. If
> > any
> > > > changes happen to the topology during establishing process, user will
> > be
> > > > notified and allowed to proceed or abort the procedure.
> > > >
> > > > Second method allows to use some monitori
onitoring'n'management tools like
> > > WebConsole where user can prepare a list of nodes, using them create a
> BT
> > > and send to the cluster a command to finally establish it.
> > >
> > > From high level BaselineTopology entity contains only
gt;
> > *BaselineTopology {*
> > * Collection nodes;*
> > *}*
> >
> > *TopologyNode* here contains information about node - its consistent id
> and
> > set of user attributes used to calculate affinity function.
> >
> >
> >
> >
> > --
> > View this message in context: http://apache-ignite-
> > developers.2346864.n4.nabble.com/Cluster-auto-activation-
> > design-proposal-tp20295p21066.html
> > Sent from the Apache Ignite Developers mailing list archive at
> Nabble.com.
> >
>
gt;
> *TopologyNode* here contains information about node - its consistent id and
> set of user attributes used to calculate affinity function.
>
>
>
>
> --
> View this message in context: http://apache-ignite-
> developers
rs.2346864.n4.nabble.com/Cluster-auto-activation-design-proposal-tp20295p21066.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
On Thu, Aug 17, 2017 at 7:34 AM, Sergey Chugunov
wrote:
> Dmitriy,
>
> As automatic creation of Baseline Topology is just another use case about
> the whole concept, lets discuss it in this thread and forget about parallel
> one.
>
> *initialActivationNodes* for desired configuration of Baseline
Dmitriy,
As automatic creation of Baseline Topology is just another use case about
the whole concept, lets discuss it in this thread and forget about parallel
one.
*initialActivationNodes* for desired configuration of Baseline Topology
sounds good to me, I would like to hear from other Igniters.
Sergey,
As it is becoming clear from another thread, the only configuration users
will need to provide is the initial set of nodes. Everything else will be
handled by Ignite automatically.
In this case, the name Baseline Topology will appear only in documentation,
in which case the name is OK (th
More options to name the concept (one may put "node set" or "topology" at
the end - for me these are interchangeable):
1. essential
2. basic
3. completed
4. prepared
5. solid
6. enduring
To me the name must stress the fact that "node set" or "topology" contains
all nodes user i
Going down "node set" road:
-fixed node set
-established node set
-base node set
On Thu, Aug 10, 2017 at 5:23 PM, Dmitriy Setrakyan
wrote:
> Can we brainstorm on the names again, I am not sure we have a consensus on
> the name "baseline topology". This will be included in Ignite
> configuration
Can we brainstorm on the names again, I am not sure we have a consensus on
the name "baseline topology". This will be included in Ignite
configuration, so the name has to be clear.
Some of the proposals were:
- baseline topology
- minimal node set
- node restart set
- minimal topology
Any other
Denis,
This should be handled by the BT triggers. If I have 3 backups configured,
I actually won't care if my cluster will live 6 hours without an additional
backup. If for a partition there is only one backup left - a new BT should
be triggered automatically.
2017-08-10 0:33 GMT+03:00 Denis Magd
Sergey,
That’s the only concern I have:
* 5. User takes out nodes from cluster (e.g. for maintenance purposes): no
rebalance happens until user recreates BLT on new cluster topology.*
What if a node is crashed (or some other kind of outage) in the middle of the
night and the user has to be su
Folks,
I've summarized all results from our discussion so far on wiki page:
https://cwiki.apache.org/confluence/display/IGNITE/Automatic+activation+design+-+draft
I hope I reflected the most important details and going to add API
suggestions for all use cases soon.
Feel free to give feedback her
Hi,
>>1. User creates new BLT using WebConsole or other tool and "applies" it
to brand-new cluster.
Good idea, but we also should implement *command-line utility* for the same
use case.
--
Alexey Kuznetsov
I also would like to provide more use cases of how BLT is supposed to work
(let me call it this way until we come up with a better one):
1. User creates new BLT using WebConsole or other tool and "applies" it
to brand-new cluster.
2. User starts up brand-new cluster with desired amount o
My understanding of Baseline Topology is the set of nodes which are
*expected* to be in the cluster.
Let me go a little bit further because BT (or whatever name we choose) may
and will solve more issues than just auto-activation:
1) More graceful control over rebalancing than just rebalance delay.
>Obvious connotation of "minimal set" is a set that cannot be decreased.
>But lets consider the following case: user has a cluster of 50 nodes and
>decides to switch off 3 nodes for maintenance for a while. Ok, user just
>does it and then recreates this "minimal node set" to only 47 nodes.
>So in
>I think it is not just restarts, this set of nodes is minimally required
for the cluster to function, no?
I don't think so. Cluster can function if there is no data loss.
--Yakov
Igniters, what about Target Node Set? Complete Node Set?
As when we reach this topology, we can activate cluster.
чт, 3 авг. 2017 г. в 12:58, Sergey Chugunov :
> Dmitriy,
>
> Obvious connotation of "minimal set" is a set that cannot be decreased.
>
> But lets consider the following case: user ha
Dmitriy,
Obvious connotation of "minimal set" is a set that cannot be decreased.
But lets consider the following case: user has a cluster of 50 nodes and
decides to switch off 3 nodes for maintenance for a while. Ok, user just
does it and then recreates this "minimal node set" to only 47 nodes.
Yakov,
I think it is not just restarts, this set of nodes is minimally required for
the cluster to function, no?
D.
On Aug 3, 2017, 11:23 AM, at 11:23 AM, Yakov Zhdanov
wrote:
>Ю> How about naming it "minimal node set" or "required node set"?
>
>Required for what? I would add restart if the
>From my standpoint name for the concept should emphasize that nodes from
the set constitute a target topology - the place where user wants to be.
If we go in a "node set" way, what about FixedNodeSet or BaseNodeSet?
"restart node set" also is a bit confusing because this concept works not
only t
Ю> How about naming it "minimal node set" or "required node set"?
Required for what? I would add restart if there are no confusion.
--Yakov
How about naming it "minimal node set" or "required node set"?
D.
On Aug 3, 2017, 11:15 AM, at 11:15 AM, Yakov Zhdanov
wrote:
>> * 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 a
> * 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 jo
First of all, this sounds a bit too scientific and will likely be
misunderstood and misused. Is there a chance to give it a better name and a
simpler use case and description?
Secondly, I do agree that it should be mandatory to update the BT. For
example, what if I want to add several nodes to the
I think we should be able to change the BT in the runtime, and a user
should have several ways to do this:
* programmatically via the API suggested by Sergey
* Using management tools (console visor on Web Console)
* Based on some sort of policies when the actual cluster topology differs
too muc
Sergey,
Is it assumed that the baseline topology can be updated in runtime? Like,
initially I had a cluster of 10 nodes but in a couple of weeks it was expanded
to 15 nodes. How the baseline topology should be updated in this way? Will it
happen automatically?
—
Denis
> On Aug 1, 2017, at 7:5
Hello Ignite developers,
I would like to start a discussion about design of important improvement
enabling automatic activation of cluster with durable store turned on [1].
Also it will help us to solve an issue with data divergence (e.g. this may
happen when half of the cluster goes down and upda
49 matches
Mail list logo
