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

Pravega Operator post controller-runtime upgrade does not handle Segment Store STS upgrade one at a time #477

Closed
SrishT opened this issue Nov 10, 2020 · 0 comments · Fixed by #478
Closed

Pravega Operator post controller-runtime upgrade does not handle Segment Store STS upgrade one at a time #477

SrishT opened this issue Nov 10, 2020 · 0 comments · Fixed by #478
Assignees
@SrishT

Comments

@SrishT
Copy link
Contributor

SrishT commented Nov 10, 2020

Description

Pravega Operator adopts an OnDelete upgrade strategy to handle segmentstore upgrade in which segmentstore pods are brought down one at a time and the updated pod comes back up. However from Pravega Operator version 0.5.0 onwards, it has been observed that multiple segmentstore pods are being brought down when an upgrade is triggered, which might be detrimental.

Importance

must have

Location

pkg/controller/pravegacluster/upgrade.go
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SrishT SrishT

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Issue 477: Handling Segmentstore STS upgrade pravega/pravega-operator
1 participant
@SrishT