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 <dma...@apache.org> 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 <ivan.glu...@gmail.com> 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. >>
