Operator fails "silently" to update Druid Cluster's resource
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- kubernetes, rust
- Domain
- infrastructure
Research direction
Start at the custom resource reconciliation path for Druid cluster resource changes and trace how the StatefulSet handles data storage size updates. Reproduce a data-storage change and compare it with CPU or memory changes; done means the operator applies the storage change without silently leaving the StatefulSet unchanged, while preserving the PVCs.
Written by the indexing model from the issue text.
Description
Affected version
No response
Current and expected behavior
I could recreate the problem when changing the "data" storage size.Changing CPU or Memory resources seems to work (results in a Pod restart).
Possible solution
In order to capture this we either need webhooks or track the resources in the status of the custom resource and delete and recreate the statefulset (PVCs should be resized automatically?).
Additional context
No response
Environment
No response
Would you like to work on fixing this bug?
None
- Dominant language
- Rust
- Stars
- 12
- Forks
- 1
- Avg merge
- 16h 22m
- Merged PRs (30d)
- 13
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stackabletech/druid-operator
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
stackabletech/druid-operator#905 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
stackabletech/druid-operator#692 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
stackabletech/druid-operator#647 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
stackabletech/druid-operator#646 ·
Maintainers usually reply within 1 day
-
type/bug
Difficulty 5/5 Over a week Newbie friendliness 20/100
stackabletech/druid-operator#606 · 3 comments ·
Maintainers usually reply within 1 day
All issues in stackabletech/druid-operator
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
AstrBotDevs/AstrBot-desktop#197 ·
-
area:breg enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
registrystack/registry-stack#2765 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
stackabletech/airflow-operator#898 ·
Maintainers usually reply within 1 day