Hi, as I see in 1.12 release, there were bigger impacts in membership part of code with:
"Move the membership code into a separate gradle sub-project" https://issues.apache.org/jira/browse/GEODE-6883 Maybe to check is this connected to reported bug. BR, Mario ________________________________ Šalje: Alberto Gomez <alberto.go...@est.tech> Poslano: 8. lipnja 2020. 9:29 Prima: dev@geode.apache.org <dev@geode.apache.org> Predmet: Re: Problem in rolling upgrade since 1.12 Hi, I attach a diff for the modified test case in case you would like to use it to check the problem I mentioned. BR, Alberto ________________________________ From: Alberto Gomez <alberto.go...@est.tech> Sent: Saturday, June 6, 2020 4:06 PM To: dev@geode.apache.org <dev@geode.apache.org> Subject: Problem in rolling upgrade since 1.12 Hi, I have observed that since version 1.12 rolling upgrades to future versions leave the first upgraded locator "as if" it was still on version 1.12. This is the output from "list members" before starting the upgrade from version 1.12: Name | Id ---- | ----------------------------------------------------------- vm2 | 192.168.0.37(vm2:29367:locator)<ec><v0>:41001 [Coordinator] vm0 | 192.168.0.37(vm0:29260)<v1>:41002 vm1 | 192.168.0.37(vm1:29296)<v2>:41003 And this is the output from "list members" after upgrading the first locator from 1.12 to 1.13/1.14: Name | Id ---- | -------------------------------------------------------------------------------- vm2 | 192.168.0.37(vm2:1453:locator)<ec><v8>:41001(version:GEODE 1.12.0) [Coordinator] vm0 | 192.168.0.37(vm0:810)<v1>:41002(version:GEODE 1.12.0) vm1 | 192.168.0.37(vm1:849)<v2>:41003(version:GEODE 1.12.0) Finally this is the output in gfsh once the rolling upgrade has been completed (locators and servers upgraded): Name | Id ---- | -------------------------------------------------------------------------------- vm2 | 192.168.0.37(vm2:1453:locator)<ec><v8>:41001(version:GEODE 1.12.0) [Coordinator] vm0 | 192.168.0.37(vm0:2457)<v23>:41002 vm1 | 192.168.0.37(vm1:2576)<v25>:41003 I verified this by running manual tests and also by running the following upgrade test (had to stop it in the middle to connect via gfsh and get the gfsh outputs): RollingUpgradeRollServersOnPartitionedRegion_dataserializable.testRollServersOnPartitionedRegion_dataserializable After the rolling upgrade, the shutdown command fails with the following error: Member 192.168.0.37(vm2:1453:locator)<ec><v8>:41001 could not be found. Please verify the member name or ID and try again. The only way I have found to come out of the situation is by restarting the locator. Once restarted again, the output of gfsh shows that all members are upgraded to the new version, i.e. the locator does not show anymore that it is on version GEODE 1.12.0. Anybody has any clue why this is happening? Thanks in advance, /Alberto G.
