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

Campactor should work directly on object storage #1673

Closed
oded-dd opened this issue Oct 22, 2019 · 2 comments
Closed

Campactor should work directly on object storage #1673

oded-dd opened this issue Oct 22, 2019 · 2 comments

Comments

@oded-dd
Copy link

oded-dd commented Oct 22, 2019

Currently we encounter an issue where the compactor requires a disk for the compaction process. Once finished the disk can be deleted as the data is not needed there any more. This work can be done on S3 directly instead. As the work is asynchronous we will pay in CPU but it should not be expansive as this is a batch running from time to time. Managing the disk locally is not to complicated but does not make sense in this case as the compactor should be decoupled from Prometheus entirely.

@bwplotka bwplotka changed the title Campactor should use S3 instead of a local storage Campactor should work directly on object storage Oct 22, 2019
@GiedriusS
Copy link
Member

Perhaps the proposal (code) here #1567 could be reused?

@stale
Copy link

stale bot commented Jan 11, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jan 11, 2020
@stale stale bot closed this as completed Jan 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants