Hint for user that baseline topology should be changed in order to trigger rebalance

[Ivan Rakov]

Folks,

Since 2.4, Ignite cluster requires baseline topology in persistent mode.
That means if user wants to scale cluster and add more nodes, data won't be
redistributed among the whole node set until manual call of
IgniteCluster#setBaselineTopology.

Surely this behavior is well-documented, but don't we need to give user a
hint that baseline topology should be managed manually? I think, log
message with something like "Current set of nodes differs from baseline
topology, please call XXX in order to trigger rebalance and redistribute
your data" will make the situation a bit more transparent.

Right now we have only this message

> [2020-01-07T19:36:45,997][INFO
> ][exchange-worker-#39%blue-54.158.100.161%][GridCachePartitionExchangeManager] Skipping
> rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=2,
> minorTopVer=0], force=false, evt=NODE_JOINED, node=57bc10fe-1505-4e8e-9987-
> 52c9c903c6ef]

which doesn't properly explain what's going on.

[slava.koptilin]

Hello,

I think, log
> message with something like "Current set of nodes differs from baseline
> topology, please call XXX in order to trigger rebalance and redistribute
> your data" will make the situation a bit more transparent.

Yes, this seems reasonable to me when the baseline auto-adjust feature is
disabled.

Thanks,
S.

чт, 9 янв. 2020 г. в 17:21, Ivan Rakov <[hidden email]>:

> Folks,
>
> Since 2.4, Ignite cluster requires baseline topology in persistent mode.
> That means if user wants to scale cluster and add more nodes, data won't be
> redistributed among the whole node set until manual call of
> IgniteCluster#setBaselineTopology.
>
> Surely this behavior is well-documented, but don't we need to give user a
> hint that baseline topology should be managed manually? I think, log
> message with something like "Current set of nodes differs from baseline
> topology, please call XXX in order to trigger rebalance and redistribute
> your data" will make the situation a bit more transparent.
>
> Right now we have only this message
>
> > [2020-01-07T19:36:45,997][INFO
> >
> ][exchange-worker-#39%blue-54.158.100.161%][GridCachePartitionExchangeManager]
> Skipping
> > rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=2,
> > minorTopVer=0], force=false, evt=NODE_JOINED,
> node=57bc10fe-1505-4e8e-9987-
> > 52c9c903c6ef]
>
> which doesn't properly explain what's going on.
>

[Ilya Kasnacheev]

Hello!

Can we perhaps add this as a blocker to 2.8?

Perhaps by correlating with
https://issues.apache.org/jira/browse/IGNITE-12504

Regards,
--
Ilya Kasnacheev


чт, 9 янв. 2020 г. в 17:59, Вячеслав Коптилин <[hidden email]>:

> Hello,
>
> I think, log
> > message with something like "Current set of nodes differs from baseline
> > topology, please call XXX in order to trigger rebalance and redistribute
> > your data" will make the situation a bit more transparent.
>
> Yes, this seems reasonable to me when the baseline auto-adjust feature is
> disabled.
>
> Thanks,
> S.
>
> чт, 9 янв. 2020 г. в 17:21, Ivan Rakov <[hidden email]>:
>
> > Folks,
> >
> > Since 2.4, Ignite cluster requires baseline topology in persistent mode.
> > That means if user wants to scale cluster and add more nodes, data won't
> be
> > redistributed among the whole node set until manual call of
> > IgniteCluster#setBaselineTopology.
> >
> > Surely this behavior is well-documented, but don't we need to give user a
> > hint that baseline topology should be managed manually? I think, log
> > message with something like "Current set of nodes differs from baseline
> > topology, please call XXX in order to trigger rebalance and redistribute
> > your data" will make the situation a bit more transparent.
> >
> > Right now we have only this message
> >
> > > [2020-01-07T19:36:45,997][INFO
> > >
> >
> ][exchange-worker-#39%blue-54.158.100.161%][GridCachePartitionExchangeManager]
> > Skipping
> > > rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=2,
> > > minorTopVer=0], force=false, evt=NODE_JOINED,
> > node=57bc10fe-1505-4e8e-9987-
> > > 52c9c903c6ef]
> >
> > which doesn't properly explain what's going on.
> >
>

[dmagda]

Ivan, Igniters, thanks for starting the discussion,

How about the following a bit simplified message template? It's assumed the
user is aware of what both rebalancing and baseline topology mean.

"New server node joined the cluster, add it to the baseline topology
manually to trigger data rebalancing [node details]"

a complete message will look like this

"New server node joined the cluster, add it to the baseline topology
manually to trigger data rebalancing [[topVer=2, minorTopVer=0],
force=false, evt=NODE_JOINED, node=57bc10fe-1505-4e8e-9987-52c9c903c6ef]]


-
Denis


On Thu, Jan 9, 2020 at 6:21 AM Ivan Rakov <[hidden email]> wrote:

> Folks,
>
> Since 2.4, Ignite cluster requires baseline topology in persistent mode.
> That means if user wants to scale cluster and add more nodes, data won't be
> redistributed among the whole node set until manual call of
> IgniteCluster#setBaselineTopology.
>
> Surely this behavior is well-documented, but don't we need to give user a
> hint that baseline topology should be managed manually? I think, log
> message with something like "Current set of nodes differs from baseline
> topology, please call XXX in order to trigger rebalance and redistribute
> your data" will make the situation a bit more transparent.
>
> Right now we have only this message
>
> > [2020-01-07T19:36:45,997][INFO
> >
> ][exchange-worker-#39%blue-54.158.100.161%][GridCachePartitionExchangeManager]
> Skipping
> > rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=2,
> > minorTopVer=0], force=false, evt=NODE_JOINED,
> node=57bc10fe-1505-4e8e-9987-
> > 52c9c903c6ef]
>
> which doesn't properly explain what's going on.
>

[Stanislav Lukyanov]

We already have a ticket for this open BTW: https://issues.apache.org/jira/browse/IGNITE-8115 <https://issues.apache.org/jira/browse/IGNITE-8115>.

I would also avoid saying anything about rebalancing - at this point the user may not know what it is.
This message is very clearly targeted at new users, so it is probably wrong to assume that they know
what baseline topology or rebalancing is.

I think it's better to say something like "add it to the baseline topology if you want it to store data. See <docs link> for details.".

Stan

> On 9 Jan 2020, at 23:28, Denis Magda <[hidden email]> wrote:
>
> Ivan, Igniters, thanks for starting the discussion,
>
> How about the following a bit simplified message template? It's assumed the
> user is aware of what both rebalancing and baseline topology mean.
>
> "New server node joined the cluster, add it to the baseline topology
> manually to trigger data rebalancing [node details]"
>
> a complete message will look like this
>
> "New server node joined the cluster, add it to the baseline topology
> manually to trigger data rebalancing [[topVer=2, minorTopVer=0],
> force=false, evt=NODE_JOINED, node=57bc10fe-1505-4e8e-9987-52c9c903c6ef]]
>
>
> -
> Denis
>
>
> On Thu, Jan 9, 2020 at 6:21 AM Ivan Rakov <[hidden email]> wrote:
>
>> Folks,
>>
>> Since 2.4, Ignite cluster requires baseline topology in persistent mode.
>> That means if user wants to scale cluster and add more nodes, data won't be
>> redistributed among the whole node set until manual call of
>> IgniteCluster#setBaselineTopology.
>>
>> Surely this behavior is well-documented, but don't we need to give user a
>> hint that baseline topology should be managed manually? I think, log
>> message with something like "Current set of nodes differs from baseline
>> topology, please call XXX in order to trigger rebalance and redistribute
>> your data" will make the situation a bit more transparent.
>>
>> Right now we have only this message
>>
>>> [2020-01-07T19:36:45,997][INFO
>>>
>> ][exchange-worker-#39%blue-54.158.100.161%][GridCachePartitionExchangeManager]
>> Skipping
>>> rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=2,
>>> minorTopVer=0], force=false, evt=NODE_JOINED,
>> node=57bc10fe-1505-4e8e-9987-
>>> 52c9c903c6ef]
>>
>> which doesn't properly explain what's going on.
>>

[dmagda]

Stan,

I would not suggest us adding any links to docs as long as the message
needs to be self-explanatory. If someone doesn't get it then they should
google. Taking your feedback into consideration:

"New server node joined the cluster, add it to the baseline topology to
store data there  [[topVer=2, minorTopVer=0], force=false, evt=NODE_JOINED,
node=57bc10fe-1505-4e8e-9987-52c9c903c6ef]]

*Artem*, could you share your thoughts on this? *Ivan*, what's your
thinking?

-
Denis


On Mon, Jan 13, 2020 at 5:27 AM Stanislav Lukyanov <[hidden email]>
wrote:

> We already have a ticket for this open BTW:
> https://issues.apache.org/jira/browse/IGNITE-8115 <
> https://issues.apache.org/jira/browse/IGNITE-8115>.
>
> I would also avoid saying anything about rebalancing - at this point the
> user may not know what it is.
> This message is very clearly targeted at new users, so it is probably
> wrong to assume that they know
> what baseline topology or rebalancing is.
>
> I think it's better to say something like "add it to the baseline topology
> if you want it to store data. See <docs link> for details.".
>
> Stan
>
> > On 9 Jan 2020, at 23:28, Denis Magda <[hidden email]> wrote:
> >
> > Ivan, Igniters, thanks for starting the discussion,
> >
> > How about the following a bit simplified message template? It's assumed
> the
> > user is aware of what both rebalancing and baseline topology mean.
> >
> > "New server node joined the cluster, add it to the baseline topology
> > manually to trigger data rebalancing [node details]"
> >
> > a complete message will look like this
> >
> > "New server node joined the cluster, add it to the baseline topology
> > manually to trigger data rebalancing [[topVer=2, minorTopVer=0],
> > force=false, evt=NODE_JOINED, node=57bc10fe-1505-4e8e-9987-52c9c903c6ef]]
> >
> >
> > -
> > Denis
> >
> >
> > On Thu, Jan 9, 2020 at 6:21 AM Ivan Rakov <[hidden email]> wrote:
> >
> >> Folks,
> >>
> >> Since 2.4, Ignite cluster requires baseline topology in persistent mode.
> >> That means if user wants to scale cluster and add more nodes, data
> won't be
> >> redistributed among the whole node set until manual call of
> >> IgniteCluster#setBaselineTopology.
> >>
> >> Surely this behavior is well-documented, but don't we need to give user
> a
> >> hint that baseline topology should be managed manually? I think, log
> >> message with something like "Current set of nodes differs from baseline
> >> topology, please call XXX in order to trigger rebalance and redistribute
> >> your data" will make the situation a bit more transparent.
> >>
> >> Right now we have only this message
> >>
> >>> [2020-01-07T19:36:45,997][INFO
> >>>
> >>
> ][exchange-worker-#39%blue-54.158.100.161%][GridCachePartitionExchangeManager]
> >> Skipping
> >>> rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=2,
> >>> minorTopVer=0], force=false, evt=NODE_JOINED,
> >> node=57bc10fe-1505-4e8e-9987-
> >>> 52c9c903c6ef]
> >>
> >> which doesn't properly explain what's going on.
> >>
>
>

[Artem Budnikov-2]

Hi everyone,

I think a link to the documentation is unnecessary. We could simply
mention "baseline topology", and users will be able to find what it is
in the docs.

Artem Budnikov
Technical Writer
gridgain.com

On 13.01.2020 21:15, Denis Magda wrote:

> Stan,
>
> I would not suggest us adding any links to docs as long as the message
> needs to be self-explanatory. If someone doesn't get it then they
> should google. Taking your feedback into consideration:
>
> "New server node joined the cluster, add it to the baseline topology
> to store data there  [[topVer=2, minorTopVer=0], force=false,
> evt=NODE_JOINED, node=57bc10fe-1505-4e8e-9987-52c9c903c6ef]]
>
> *Artem*, could you share your thoughts on this? *Ivan*, what's your
> thinking?
>
> -
> Denis
>
>
> On Mon, Jan 13, 2020 at 5:27 AM Stanislav Lukyanov
> <[hidden email] <mailto:[hidden email]>> wrote:
>
>     We already have a ticket for this open BTW:
>     https://issues.apache.org/jira/browse/IGNITE-8115
>     <https://issues.apache.org/jira/browse/IGNITE-8115>.
>
>     I would also avoid saying anything about rebalancing - at this
>     point the user may not know what it is.
>     This message is very clearly targeted at new users, so it is
>     probably wrong to assume that they know
>     what baseline topology or rebalancing is.
>
>     I think it's better to say something like "add it to the baseline
>     topology if you want it to store data. See <docs link> for details.".
>
>     Stan
>
>     > On 9 Jan 2020, at 23:28, Denis Magda <[hidden email]
>     <mailto:[hidden email]>> wrote:
>     >
>     > Ivan, Igniters, thanks for starting the discussion,
>     >
>     > How about the following a bit simplified message template? It's
>     assumed the
>     > user is aware of what both rebalancing and baseline topology mean.
>     >
>     > "New server node joined the cluster, add it to the baseline topology
>     > manually to trigger data rebalancing [node details]"
>     >
>     > a complete message will look like this
>     >
>     > "New server node joined the cluster, add it to the baseline topology
>     > manually to trigger data rebalancing [[topVer=2, minorTopVer=0],
>     > force=false, evt=NODE_JOINED,
>     node=57bc10fe-1505-4e8e-9987-52c9c903c6ef]]
>     >
>     >
>     > -
>     > Denis
>     >
>     >
>     > On Thu, Jan 9, 2020 at 6:21 AM Ivan Rakov <[hidden email]
>     <mailto:[hidden email]>> wrote:
>     >
>     >> Folks,
>     >>
>     >> Since 2.4, Ignite cluster requires baseline topology in
>     persistent mode.
>     >> That means if user wants to scale cluster and add more nodes,
>     data won't be
>     >> redistributed among the whole node set until manual call of
>     >> IgniteCluster#setBaselineTopology.
>     >>
>     >> Surely this behavior is well-documented, but don't we need to
>     give user a
>     >> hint that baseline topology should be managed manually? I
>     think, log
>     >> message with something like "Current set of nodes differs from
>     baseline
>     >> topology, please call XXX in order to trigger rebalance and
>     redistribute
>     >> your data" will make the situation a bit more transparent.
>     >>
>     >> Right now we have only this message
>     >>
>     >>> [2020-01-07T19:36:45,997][INFO
>     >>>
>     >>
>     ][exchange-worker-#39%blue-54.158.100.161%][GridCachePartitionExchangeManager]
>     >> Skipping
>     >>> rebalancing (nothing scheduled) [top=AffinityTopologyVersion
>     [topVer=2,
>     >>> minorTopVer=0], force=false, evt=NODE_JOINED,
>     >> node=57bc10fe-1505-4e8e-9987-
>     >>> 52c9c903c6ef]
>     >>
>     >> which doesn't properly explain what's going on.
>     >>
>

[fi1ipx]

Hello folks!

I'm a new community member and tried to solve the issue as a first
introduction task.

I've got this log message:
"Local node is not included in Baseline Topology and will not be used for
data storage. Use control.(sh|bat) script or IgniteCluster interface to
include the node to Baseline Topology." when started an additional node
after a cluster was activated.

I suppose the message explains the situation quite well.



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[fi1ipx]

I closed the ticket ignite-8115 because it's duplicating ignite-8190. In
the ticket ignite-8190 requested functionality is already done.

Thanks!

On Wed, Jan 15, 2020 at 1:26 PM fi1ipx <[hidden email]> wrote:

> Hello folks!
>
> I'm a new community member and tried to solve the issue as a first
> introduction task.
>
> I've got this log message:
> "Local node is not included in Baseline Topology and will not be used for
> data storage. Use control.(sh|bat) script or IgniteCluster interface to
> include the node to Baseline Topology." when started an additional node
> after a cluster was activated.
>
> I suppose the message explains the situation quite well.
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>