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.

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

rollout-operator: faster scale down of prepared ingesters #155

Closed
pstibrany opened this issue Jun 14, 2024 · 0 comments · Fixed by #156
Closed

rollout-operator: faster scale down of prepared ingesters #155

pstibrany opened this issue Jun 14, 2024 · 0 comments · Fixed by #156

Comments

@pstibrany
Copy link
Member

Rollout-operator currently allows "delayed downscale" if delay has elapsed for all downscaled replicas. For example for following ingest-storage partitions:

image

maximum timestamp when downscale was initiated is `2024-05-07 04:10:00 UTC`, and that tells rollout-operator to wait for delay since this timestamp -- with 13h delay, that would be `2024-05-07 17:10:00 UTC`.

However some partitions started to downscale earlier. Specifically partitions 42 – 46 (and corresponding ingesters) could be downscaled after delay since 2024-05-06 12:59:47. With 13h delay that would be 2024-05-07 01:59:47.

This issue is about implementing these earlier downscales for pods "at the end of statefulset" that could be downscaled earlier. In other words, when statefulset is asked to downscale from N to M replicas, we can compute MaxPrepareTimestamp for pods [M..N], [M+1..N], [M+2..N], and if delay has elapsed for any of these, we could downscale given group, even if we can't yet downscale to M pods.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant