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

Investigate high object count in cloud storage cache #12980

Closed
abhijat opened this issue Aug 24, 2023 · 0 comments · Fixed by #13013
Closed

Investigate high object count in cloud storage cache #12980

abhijat opened this issue Aug 24, 2023 · 0 comments · Fixed by #13013
Assignees
Labels
area/cloud-storage Shadow indexing subsystem kind/enhance New feature or request remediation Incident follow-ups that also show up in Incident.io when this label is used. sev/medium Bugs that do not meet criteria for high or critical, but are more severe than low.

Comments

@abhijat
Copy link
Contributor

abhijat commented Aug 24, 2023

Investigate high storage count in cloud storage cache seen in certain clusters. Additionally come up with a strategy to make such clusters cope with the new object count restriction.

@abhijat abhijat added kind/bug Something isn't working kind/enhance New feature or request area/cloud-storage Shadow indexing subsystem and removed kind/bug Something isn't working labels Aug 24, 2023
@abhijat abhijat self-assigned this Aug 24, 2023
@abhijat abhijat added sev/medium Bugs that do not meet criteria for high or critical, but are more severe than low. remediation Incident follow-ups that also show up in Incident.io when this label is used. labels Aug 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/cloud-storage Shadow indexing subsystem kind/enhance New feature or request remediation Incident follow-ups that also show up in Incident.io when this label is used. sev/medium Bugs that do not meet criteria for high or critical, but are more severe than low.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant