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

Receive: initialize default tenant on start in receiver #6728

Conversation

MichaHoffmann
Copy link
Contributor

  • I added CHANGELOG entry for this change.
  • Change is not relevant to the end user.

Changes

Initialize default tenant when starting receiver so we dont fail writes while starting the tsdb.

Verification

Not yet

@yeya24
Copy link
Contributor

yeya24 commented Oct 23, 2023

Initialize default tenant when starting receiver so we dont fail writes while starting the tsdb.

What caused the writes to fail? Because the default tenant's TSDB has not been initialized?

Then the problem exits for all tenants. Feels like not that useful by initializing default tenant only.

@MichaHoffmann
Copy link
Contributor Author

Initialize default tenant when starting receiver so we dont fail writes while starting the tsdb.

What caused the writes to fail? Because the default tenant's TSDB has not been initialized?

Then the problem exits for all tenants. Feels like not that useful by initializing default tenant only.

But its the one tenant that we know before already

@yeya24
Copy link
Contributor

yeya24 commented Oct 23, 2023

But its the one tenant that we know before already

Why? Default tenant might not even exists. We should be able to persist existing tenant information somewhere at receiver

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 this pull request may close these issues.

2 participants