Understood. But adding some kind of merge policy (keeping latest entry and ignore other copies) and allowing node rejoin may be good option.
Thanks. On 28 December 2016 at 21:33, vkulichenko <[email protected]> wrote: > Hi Anil, > > Because that's how it works :) Main reason behind this is to ensure data > consistency. When you restart the node, its memory is cleaned up and it > joins as a brand new node. Rejoin with existing data will require > additional > processing and in general case will not guarantee consistency. > > Makes sense? > > -Val > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Ignite-cluster-tp9527p9784.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
