Note that, if you’re using persistence, the recommendation is to use StatefulSets so that the nodes are added/removed in a predictable way.
https://apacheignite.readme.io/docs/stateful-deployment <https://apacheignite.readme.io/docs/stateful-deployment> Regards, Stephen > On 14 Feb 2019, at 15:18, Ilya Kasnacheev <[email protected]> wrote: > > Hello! > > If you have backups factor of 1 then you can stop a node without data loss, > then wait until rebalance is complete. So you should only remove nodes by > one. You can add multiple ones at a time. > > Unfortunately there is no way to take node out of topology without stopping > it. > > Regards, > -- > Ilya Kasnacheev > > > пн, 11 февр. 2019 г. в 10:08, ashfaq <[email protected] > <mailto:[email protected]>>: > Hi , > > We are using ignite in our architecture in kubernetes environment. In our > current development phase I am working on scale out and scale in of ignite > nodes automatically when the event is triggered. > > Could you please give me the steps for scale out and scale in with out any > data loss. Also the steps to verify if the event is successfully completed. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > <http://apache-ignite-users.70518.x6.nabble.com/>
