Alexey, > All scenarios where rebalanceDelay has meaning are handled by baseline > topology now.
Can you, please, provide more details here e.g. the whole list of scenarios where rebalanceDelay is used and how these handled by baseline topology? Actually, I doubt that it covers exactly all the cases due to rebalanceDelay is a "per cache group property" rather than "baseline" is meaningful for the whole topology. On Wed, 12 Feb 2020 at 12:58, Alexei Scherbakov <alexey.scherbak...@gmail.com> wrote: > > I've meant baseline topology. > > ср, 12 февр. 2020 г. в 12:41, Alexei Scherbakov < > alexey.scherbak...@gmail.com>: > > > > > V.Pyatkov > > > > Doesn't rebalance topology solves it ? > > > > ср, 12 февр. 2020 г. в 12:31, V.Pyatkov <vldpyat...@gmail.com>: > > > >> Hi, > >> > >> I am sure we can to reduce this ability, but do not completely. > >> We can use rebalance delay for disable it until manually triggered. > >> > >> CacheConfiguration#setRebalanceDelay(-1) > >> > >> It may helpful for cluster where can not allow performance drop from > >> rebalance at any time. > >> > >> > >> > >> -- > >> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ > >> > > > > > > -- > > > > Best regards, > > Alexei Scherbakov > > > > > -- > > Best regards, > Alexei Scherbakov
