Skip to content

Different priority levels for system segments vs external segments. #5260

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

Closed
andreipaduroiu opened this issue Oct 16, 2020 · 0 comments · Fixed by #5268
Closed

Different priority levels for system segments vs external segments. #5260

andreipaduroiu opened this issue Oct 16, 2020 · 0 comments · Fixed by #5268
Assignees
Labels

Comments

@andreipaduroiu
Copy link
Member

Problem description
System segments must bypass throttling checks and any operations on them should be executed before external operations.

This should ease up self-induced cache pressure and speed up LTS transfers for SLTS implementations.

Problem location
Segment Store/Ingestion Pipeline.

Suggestions for an improvement
Implement basic QoS. Define at least 2 priorities (Normal and System). System is assigned to critical, internal segments, everyone else gets Normal. Critical segments are not subject to throttling and, outside of that, would be processed ahead of other operations.

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

Successfully merging a pull request may close this issue.

1 participant