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.

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

Improved message of VersionMismatchException in validateJoinRequest() #11603

Merged
merged 1 commit into from
Oct 18, 2017
Merged

Improved message of VersionMismatchException in validateJoinRequest() #11603

merged 1 commit into from
Oct 18, 2017

Conversation

Donnerbart
Copy link
Contributor

@Donnerbart Donnerbart commented Oct 17, 2017

  • added a hint that Rolling Member Upgrades are only supported in Hazelcast Enterprise
  • added a hint that Rolling Member Upgrades are only supported for same major versions
  • added a hint that Rolling Member Upgrades are only supported for the next minor version

Examples:

  • VersionMismatchException: Joining node's version 3.11.0 is not compatible with cluster version 3.10 (Rolling Member Upgrades are only supported in Hazelcast Enterprise)
  • VersionMismatchException: Joining node's version 3.9.0 is not compatible with cluster version 3.10 (Rolling Member Upgrades are only supported for the next minor version) (Rolling Member Upgrades are only supported in Hazelcast Enterprise)
  • VersionMismatchException: Joining node's version 4.10.0 is not compatible with cluster version 3.10 (Rolling Member Upgrades are only supported for the same major version) (Rolling Member Upgrades are only supported in Hazelcast Enterprise)

Fixes #11602

* added a hint that Rolling Member Upgrades are only supported in
  Hazelcast Enterprise
* added a hint that Rolling Member Upgrades are only supported for
  same major versions
* added a hint that Rolling Member Upgrades are only supported for
  the next minor version
Copy link
Contributor

@Holmistr Holmistr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very nice, much clearer now.
One concern that comes to my mind is that when the exception is thrown and the node doesn't get joined, you can see only WARNING in the logs. I think this is a proper ERROR situation. However, I'm approving this since it's not critical, but maybe something that should be kept in mind for later.

@Donnerbart Donnerbart merged commit 999b064 into hazelcast:master Oct 18, 2017
@Donnerbart Donnerbart deleted the improvedVersionMismatchExceptionMessage branch October 18, 2017 09:53
@mmedenjak mmedenjak added the Source: Internal PR or issue was opened by an employee label Apr 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Source: Internal PR or issue was opened by an employee Team: Core Type: Enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Doing rolling upgrade without enterprise key should produce better error message
4 participants