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

Receiving tenantID single-tenant not found #94

Closed
joe-elliott opened this issue Mar 10, 2020 · 1 comment · Fixed by #321
Closed

Receiving tenantID single-tenant not found #94

joe-elliott opened this issue Mar 10, 2020 · 1 comment · Fixed by #321
Assignees

Comments

@joe-elliott
Copy link
Member

joe-elliott commented Mar 10, 2020

Reproducible locally in using tk single binary mode. Start it up and query for a trace. Something like this message will be logged

level=warn ts=2020-03-10T18:04:08.159046978Z caller=logging.go:49 traceID=32d5a7476bea519 msg="GET /api/traces/000000000000000000000000e8fb635e (500) 1.210753ms Response: \"tenantID single-tenant not found\\n\" ws: false; Accept-Encoding: gzip; User-Agent: Go-http-client/1.1; "

After the first block is cut and flushed this seems to go away.

@joe-elliott
Copy link
Member Author

joe-elliott commented Oct 28, 2020

This is due to the queriers not find the trace in the ingesters here:

https://github.com/grafana/tempo/blob/master/modules/querier/querier.go#L138

and then tempodb returning an error b/c the requested tenant does not exist.

https://github.com/grafana/tempo/blob/master/tempodb/tempodb.go#L258

When the requested tenant does not exist tempodb should return a specific "not found" error which the querier then returns as a 404.

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

Successfully merging a pull request may close this issue.

2 participants