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

Orchestrate ingestion, reaping and backfilling #202

Closed
2opremio opened this issue Jun 6, 2024 · 0 comments
Closed

Orchestrate ingestion, reaping and backfilling #202

2opremio opened this issue Jun 6, 2024 · 0 comments

Comments

@2opremio
Copy link
Contributor

2opremio commented Jun 6, 2024

Ingestion, reaping and backfilling should run independently without fighting each other.

We should create an orchestrator which coordinates them. The reaper #201 and backfiller #203 themselves are not part of this task.

The orchestrator should check the status of the history #200 and work with ingestion, reaping #201 and backfilling #203 to make sure that we never leave any gaps or inconsistencies in history.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

2 participants