You *are* changing the baseline topology. That's what autoadjust does. It automatically changes the baseline topology when a node joins or leaves the cluster.
If a node crashes or needs to be restarted for some other reason, you don't need to change the baseline. The only reason you need to change the baseline -- either automatically or manually -- is if the node is permanently going out of service (or you're adding a new node). Autoadjust is disabled for persistent clusters by default for a reason. Are you really adding or removing nodes frequently? On 16 Jul 2025, at 06:41, satyajit.man...@barclays.com wrote: Hi Stephen, Can you advise here. Also can we increase the default timeout( baselineAutoAdjustTimeout) to lets say 3 hrs before baseline autoadjustment kicks in to avoid such issues? If any nodes crashes and if it takes some time to do action and restart that node it will avoid below issue? Regards Satyajit Restricted - External *From:* Mandal, Satyajit: IT (PUN) *Sent:* Tuesday, July 15, 2025 10:09 PM *To:* user@ignite.apache.org *Subject:* RE: Query on AutoBaseLine Topology in .NET embedded service Hi Stephen, We are not changing the baseline topology. We observed in some occasion when we are restarting the crashed node after certain time the ignite log shows *df505-355c-4b5a-9c77-431b299761b2%][GridClusterStateProcessor] 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.* So question was how can we get the *ActiveBaseLineNode * number to desired state* . *Do we need to clean the wal log of that node and restart the same? Regards Satyajit *From:* Stephen Darlington <sdarling...@apache.org> *Sent:* Tuesday, July 15, 2025 8:08 PM *To:* user@ignite.apache.org *Subject:* Re: Query on AutoBaseLine Topology in .NET embedded service ------------------------------ *CAUTION:* This email originated from outside our organization - *user-return-36742-Satyajit.Mandal=barclays....@ignite.apache.org <user-return-36742-Satyajit.Mandal=barclays....@ignite.apache.org>* Do not click on links, open attachments, or respond unless you recognize the sender and can validate the content is safe. ------------------------------ The question is: why do you need to continually change the baseline topology? If you're just restarting a node -- say, for a software update -- there is no need to change the baseline. The baseline only needs to change when a node permanently comes in or out of service. Regards, Stephen On Tue, 15 Jul 2025 at 09:03, Pavel Tupitsyn <ptupit...@apache.org> wrote: I'm not an expert on this topic, sorry, let's see if someone else will chip in. On Tue, Jul 15, 2025 at 9:38 AM <satyajit.man...@barclays.com> wrote: > > Hi Pavel, > > It works most of time. Sometimes it doesn't work. The node joins the cluster but baseline toplogy doesn't changes. So need to know what are the options here to resolve this and get the baselinetopology updated? > > Regards > Satyajit > > > > > Restricted - External > -----Original Message----- > From: Pavel Tupitsyn <ptupit...@apache.org> > Sent: Tuesday, July 15, 2025 12:04 PM > To: Mandal, Satyajit: IT (PUN) <satyajit.man...@barclays.com> > Cc: user@ignite.apache.org > Subject: Re: Query on AutoBaseLine Topology in .NET embedded service > > CAUTION: This email originated from outside our organization - user-return-36737-Satyajit.Mandal=barclays....@ignite.apache.org Do not click on links, open attachments, or respond unless you recognize the sender and can validate the content is safe. > > ______________________________________________________________________ > Hi Satyajit, not sure I understand the question. > - Do you observe some unexpected behavior? > - Does baseline auto adjustment work for you or not? > > On Tue, Jul 15, 2025 at 7:32 AM <satyajit.man...@barclays.com> wrote: > > > > Hi Pavel, > > > > > > > > We are running ignite cache in embedded mode in .NET service with persistence enabled.We have enabled SetBaselineAutoAdjustEnabledFlag to true in one of the node . When we start the cluster having 6 nodes it sets AutoBaseLine. > > > > > > > > Now lets say if one node goes down and we restart the node most of the time it joins the cluster and autobaselinenodes gets adjusted . > > > > > > > > There is a case where one node goes down and after certain interval of time lets say we restart that service it joins the cluster but baseline topology doesn’t changes. Here we need advice can we set the SetBaselineAutoAdjustEnabledFlag to true and try to restart the cache to resolve this issue? . What are the alternatives? We don’t want to use control scripts. We want to handle it through configuration as we are running cache as .NET service with persistence enabled? > > > > > > > > > > > > Regards > > > > Satyajit > > > > > >
