Hi,
Thanks for your suggestion, Anthony. I gave it a try and the rolling downgrade
worked because peers are prepared to exchange messages in different versions by
means of the toDataPre_GEODE_X_X_X_X() fromDataPre_GEODE_X_X_X_X mechanism.
After all my investigation on this topic I have come to
Hi Alberto!
Another experiment that might be useful to try is changing a p2p message
following [1]. If you follow the steps in the wiki, a rolling upgrade should
work ok. But if you then try to do a rolling downgrade, what happens?
Anthony
[1]
Hi again,
I have been investigating a bit more the possibility of supporting
"rolling downgrades" in Geode similar to rolling upgrades and I would
like to share my findings and also ask for some help.
My tests were done upgrading from Geode 1.10 to a recent version in the
develop branch and
Hi Anthony,
That's an option but, as you say, the cost in infrastructure is high and
there are also other problems to solve like how to do the switch between
systems and how to assure the data consistency among them.
I was thinking that in many cases it might be possible to support a
rolling
Have you considered using a blue / green deployment approach? It provides more
flexibility for these scenarios though the infrastructure cost is high.
Anthony
> On Sep 23, 2019, at 5:59 AM, Alberto Gomez wrote:
>
> Hi,
>
> Looking at the Geode documentation I have not found any reference
Hi,
Looking at the Geode documentation I have not found any reference to
rolling back a Geode upgrade.
Running some tests, I have observed that once a Geode System has been
upgraded to a later version, it is not possible to rollback the upgrade
even if no data modifications have been done
