Replies: 4 comments 1 reply
-
possibly due to this poor choice here: https://github.com/grafana/tempo/blob/main/modules/distributor/receiver/shim.go#L312 it has just never bothered us enough to fix it. at some point a community member was working a PR to make it configurable and drastically reduce the default. at this point we could probably just remove it since we added |
Beta Was this translation helpful? Give feedback.
-
Thanks for the feedback. Should I create an issue for this? |
Beta Was this translation helpful? Give feedback.
-
Sure. Are you interested in submitting a PR to remove it? |
Beta Was this translation helpful? Give feedback.
-
Yes! I'll add that to my list, thanks for the opportunity |
Beta Was this translation helpful? Give feedback.
-
I am evaluating Tempo using docker compose
version=main-23f9d00, branch=main, revision=23f9d002f
.I have postgres, grafana, tempo, and prometheus defined with what looks like vanilla configuration for Tempo:
What I notice is that
docker compose down
is taking around 10s consistently, because Tempo takes that amount of time to shutdown. The three other services take around 0.1s to stop.I've tried to look at the ingester configuration and played with it a little bit but that 10sec shutdown "delay" still applies. Does anybody know where that could come from? Thanks!
Beta Was this translation helpful? Give feedback.
All reactions