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

storage: GC queue tuning #5252

Closed
tbg opened this issue Mar 14, 2016 · 1 comment
Closed

storage: GC queue tuning #5252

tbg opened this issue Mar 14, 2016 · 1 comment
Labels
C-performance Perf of queries or internals. Solution not expected to change functional behavior. S-1-stability Severe stability issues that can be fixed by upgrading, but usually don’t resolve by restarting
Milestone

Comments

@tbg
Copy link
Member

tbg commented Mar 14, 2016

The GC queue currently runs at regular intervals but doesn't actually get to delete much data. We should tune the threshold at which a replica is queued for GC (which is currently at one normalized units; too low).

To observe this, run the photos app for a while (single node is fine), then let the cluster idle and observe regular CPU spikes and the gc queue's event log.

@tbg tbg added this to the Beta milestone Mar 14, 2016
@petermattis petermattis modified the milestones: Beta, Q2 Apr 7, 2016
@petermattis petermattis modified the milestones: Q2, Q3 Jul 11, 2016
@petermattis petermattis added the C-performance Perf of queries or internals. Solution not expected to change functional behavior. label Jul 11, 2016
@tbg tbg added the S-1-stability Severe stability issues that can be fixed by upgrading, but usually don’t resolve by restarting label Sep 26, 2016
@spencerkimball
Copy link
Member

Closing for age and lack of actionable or pressing next steps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-performance Perf of queries or internals. Solution not expected to change functional behavior. S-1-stability Severe stability issues that can be fixed by upgrading, but usually don’t resolve by restarting
Projects
None yet
Development

No branches or pull requests

3 participants