Hi Jose. Did you test from scratch? I mean after updating a config file you should start from the clean cluster (wipe all data from all nodes), the cluster should remember its new baseline topology with new node ids. And only then try to repeat the test with one node cleaning.
I cannot promise to reproduce right now, too much work, but it looks like we also can potentially get such scenario in our environment, so when I get some time I'll try. Please share configuration files from all nodes zipped and attached here or via GitHub. Arseny Kovalchuk Senior Software Engineer at Synesis skype: arseny.kovalchuk mobile: +375 (29) 666-16-16 LinkedIn Profile <http://www.linkedin.com/in/arsenykovalchuk/en> On 23 March 2018 at 13:44, joseheitor <[email protected]> wrote: > Hi Arseny, > > Regrettably still experiencing the same results. > > Could there be something else that I am overlooking? My configurations are > quite basic - I can post them, if it will be helpful for you to duplicate > the issue... > > Thanks > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
