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

Hot upgrade between hotfix versions when running in HA #7480

Closed
lvca opened this Issue Jun 9, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@lvca
Member

lvca commented Jun 9, 2017

Today is not always safe to upgrade between hotfix versions when you're running in HA. This is because distributed protocol is not versioned. We never did it, because Hazelcast didn't support this feature, so investing in a versioned distributed protocol was worthless.

Now that Hazelcast has it, we should version our distributed protocol, so our users can upgrade a cluster of servers, one by one.

@lvca lvca added the enhancement label Jun 9, 2017

@lvca lvca added this to the 2.2.x (next hotfix) milestone Jun 9, 2017

@lvca lvca self-assigned this Jun 9, 2017

@lvca lvca referenced this issue Jun 9, 2017

Closed

Upgrade from Orient 2.2.6 to 2.2.7 #6560

0 of 4 tasks complete

lvca added a commit that referenced this issue Jun 9, 2017

@lvca lvca closed this Jun 9, 2017

@lvca

This comment has been minimized.

Show comment
Hide comment
@lvca

lvca Jun 9, 2017

Member

Implemented through the new ORemoteTaskFactoryManager interface.

Member

lvca commented Jun 9, 2017

Implemented through the new ORemoteTaskFactoryManager interface.

@robfrank robfrank modified the milestones: 2.2.x (next hotfix), 2.2.22 Jun 19, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment