Hello! You can't do that in runtime, but you can certainly remove index.bin as bulk operation.
Regards, -- Ilya Kasnacheev вт, 28 июл. 2020 г. в 08:48, Kamlesh Joshi <[email protected]>: > Thanks for the update Andrei. We upgraded from 2.6.0 to 2.7.6. > > We followed the same approach and it worked properly. > > Can we change INLINE SIZE for every cache at runtime ? > > Thanks and Regards, > Kamlesh Joshi > > > -----Original Message----- > From: aealexsandrov <[email protected]> > Sent: 27 July 2020 19:35 > To: [email protected] > Subject: [External]Re: Node left from running cluster due to > org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException: > Runtime failure on search row > > The e-mail below is from an external source. Please do not open > attachments or click links from an unknown or suspicious origin. > > Hi, > > Can you please clarify the version from which you upgraded? > > I know that it's possible that if you used a pretty old version then you > should also rebuild your indexes during the upgrade because inline size > calculation logic was changed in last releases. > > It can be done by removing index.bin files. So the logic should be the > following: > > 1)Stop the Ignite nodes. > 2)Remove index.bin files from > $IGNITE_HOME/db/<NODE_ID>/<CACHE_NAME>/index.bin > 3)Start Ignite nodes one by one. For each node wait for the following > message: > > [2020-05-29 07:55:04,984][INFO > ][build-idx-runner-#61][GridCacheDatabaseSharedManager] Indexes rebuilding > completed for all caches. > > I guess that it can help you with your upgrade. Please test it before > applying it to your production because the reason can be different. > > BR, > Andrei > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > > "Confidentiality Warning: This message and any attachments are intended > only for the use of the intended recipient(s). > are confidential and may be privileged. If you are not the intended > recipient. you are hereby notified that any > review. re-transmission. conversion to hard copy. copying. circulation or > other use of this message and any attachments is > strictly prohibited. If you are not the intended recipient. please notify > the sender immediately by return email. > and delete this message and any attachments from your system. > > Virus Warning: Although the company has taken reasonable precautions to > ensure no viruses are present in this email. > The company cannot accept responsibility for any loss or damage arising > from the use of this email or attachment." > >
