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

[ARCHIVED] Document and test storage resizing on the same nodes #825

Closed
Tracked by #1572
, #2404
...
tnozicka opened this issue Nov 8, 2021 · 4 comments · May be fixed by #2243
Closed
Tracked by #1572
, #2404
...

[ARCHIVED] Document and test storage resizing on the same nodes #825

tnozicka opened this issue Nov 8, 2021 · 4 comments · May be fixed by #2243
Labels
lifecycle/migrated-away Indicates that this issue is archived and tracking continues in a copy. priority/archived Lowest priority possible - means that the issue is archived.

Comments

@tnozicka
Copy link
Contributor

tnozicka commented Nov 8, 2021 •
edited
Loading

Given StatefulSet don't reconcile storage changes we can't yet easily handle it in the operator seamlessly and we should at least document a manual procedure. Something in the lines of:

  • orphan delete the scyllacluster
  • orphan delete the statefulsets
  • create the scyllacluster with higher storage request
  • resize the existing PVC, if the storage class supports it, replace the nodes if it doesn't
  • trigger a scyllacuster rollout
@tnozicka tnozicka added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. kind/documentation Categorizes issue or PR as related to documentation. labels Nov 8, 2021
@tnozicka tnozicka added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Nov 8, 2021
@tnozicka tnozicka added this to the v1.7 milestone Nov 8, 2021
@tnozicka tnozicka mentioned this issue Nov 12, 2021
Closed
2 tasks
@zimnx zimnx assigned Choraden and unassigned zimnx Sep 22, 2022
@Choraden Choraden mentioned this issue Oct 3, 2022
Closed
@tnozicka tnozicka removed this from the v1.7 milestone May 19, 2023
@tnozicka tnozicka mentioned this issue Nov 1, 2023
Closed
@tnozicka tnozicka mentioned this issue Nov 16, 2023
Closed
@tnozicka tnozicka changed the title Document storage resizing Document and test storage resizing on the same nodes Nov 16, 2023
@tnozicka tnozicka self-assigned this Nov 16, 2023
@scylla-operator-bot scylla-operator-bot
Copy link
Contributor

The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 30d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out

/lifecycle stale

@scylla-operator-bot scylla-operator-bot bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 1, 2024
@tnozicka
Copy link
Contributor Author

tnozicka commented Jul 1, 2024

/remove-lifecycle stale
/triage accepted

@scylla-operator-bot scylla-operator-bot bot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 1, 2024
@tnozicka tnozicka removed their assignment Nov 25, 2024
@gdubicki gdubicki mentioned this issue Dec 5, 2024
Open
@tnozicka tnozicka closed this as not planned Won't fix, can't repro, duplicate, stale Jan 2, 2025
@mflendrich mflendrich reopened this Feb 3, 2025
@mflendrich
Copy link
Collaborator

Reopened - the scope is to carry the community PR #2243 through completion.

@tnozicka tnozicka closed this as not planned Won't fix, can't repro, duplicate, stale Feb 4, 2025
@mflendrich mflendrich mentioned this issue Feb 4, 2025
Open
@mflendrich mflendrich added lifecycle/migrated-away Indicates that this issue is archived and tracking continues in a copy. priority/archived Lowest priority possible - means that the issue is archived. labels Feb 4, 2025
@mflendrich mflendrich changed the title Document and test storage resizing on the same nodes [ARCHIVED] Document and test storage resizing on the same nodes Feb 4, 2025
@mflendrich mflendrich removed kind/documentation Categorizes issue or PR as related to documentation. triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Feb 4, 2025
This was referenced Feb 4, 2025
Open
Open
@mflendrich
Copy link
Collaborator

Will be tracked in #2453.

@scylladb scylladb locked and limited conversation to collaborators Feb 4, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
lifecycle/migrated-away Indicates that this issue is archived and tracking continues in a copy. priority/archived Lowest priority possible - means that the issue is archived.
Projects
None yet
Milestone
No milestone
4 participants
@mflendrich @zimnx @tnozicka @Choraden