You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I agree the log lines are confusing, but the problem is that TSDB is never fully ready. In a sense that there can be new tenant anytime and this will create new TSDB for it. In some way in the current implementation it's expected to fail and wait for client to repeat the write.
What else we should expect here if we need to support dynamic creation of TSDBs (appendables) per tenant?
Hello 👋 Looks like there was no activity on this issue for the last two months. Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗
If there will be no activity in the next two weeks, this issue will be closed (we can always reopen an issue if we need!). Alternatively, use remind command if you wish to be reminded at some point in future.
Thanos, Prometheus and Golang version used:
Thanos: thanos-0.21.1
Object Storage Provider: N/A
What happened:
When starting new reciver cluster, we got error "get appender: TSDB not ready;"
The start script (thanos-receiver.service):
The hashring.json:
The text was updated successfully, but these errors were encountered: