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

Document rolling update considerations for multi-dc #23586

Open
patriknw opened this issue Sep 1, 2017 · 0 comments
Open

Document rolling update considerations for multi-dc #23586

patriknw opened this issue Sep 1, 2017 · 0 comments
Labels
1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted t:cluster:dc t:cluster-sharding t:rolling-updates

Comments

@patriknw
Copy link
Member

patriknw commented Sep 1, 2017

@raboof I think you tried some rolling update scenarios with the new membership multi-dc. Do recall any conclusions for that and could you add them to the documentation?

  • updating a cluster from single-dc to multi-dc
  • singleton?
  • sharding?
@patriknw patriknw added 1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted t:cluster:dc labels Sep 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted t:cluster:dc t:cluster-sharding t:rolling-updates
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@patriknw @helena