Hello, Alexey. > We need to agree whether IgniteMxBean#active(boolean) and > Ignite#active(boolean) behaving differently is ok from the user side.
I think it’s not OK. We should provide consistent behavior for all management APIs: jmx, control.sh, REST, Java API. The primary use-case I keep in mind - third party management console written in java. It will use Java API and should have an ability to execute «safe»(without data vanish) and «unsafe» deactivation. > 18 февр. 2020 г., в 12:28, Alexey Goncharuk <alexey.goncha...@gmail.com> > написал(а): > > I do not think the change size can even be an argument for not doing a > proper improvement. We need to agree whether IgniteMxBean#active(boolean) > and Ignite#active(boolean) behaving differently is ok from the user side.
