Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Cets/prevent crash on upgrade #4256

Merged
merged 3 commits into from
Apr 9, 2024
Merged

Cets/prevent crash on upgrade #4256

merged 3 commits into from
Apr 9, 2024

Commits on Apr 9, 2024

  1. Put CETS version in cluster name 

    When performing a rolling upgrade e.g. from 6.2.0 to the upcoming 6.2.1,
CETS would crash on all nodes due to version incompatibility.

This can be prevented by putting cets 'Major.Minor' version in the
cluster name, making the two cluster components disjoint during
upgrade.

The only thing to keep in mind is to bump the Major or Minor version
number when there is any incompatibility in the CETS inter-node API.
    @chrzaszcz
    chrzaszcz committed Apr 9, 2024
    Configuration menu
    Copy the full SHA
    f102499 View commit details
    Browse the repository at this point in the history

  2. Check that CETS version is added to cluster name

    @chrzaszcz
    chrzaszcz committed Apr 9, 2024
    Configuration menu
    Copy the full SHA
    e4ef412 View commit details
    Browse the repository at this point in the history

  3. Update tests with the new cluster name

    @chrzaszcz
    chrzaszcz committed Apr 9, 2024
    Configuration menu
    Copy the full SHA
    082f1e0 View commit details
    Browse the repository at this point in the history