Describe the bug
We are new to tempo, and we recently deployed tempo via helm chart in k8s cluster. We use grafana to view traces. After the deployment we noticed that we are getting timeouts when the tempo querier component tries to get/set keys from memcached.
level=error ts=2024-05-17T10:34:38.433823747Z caller=memcached.go:153 msg="Failed to get keys from memcached" err="read tcp 10.20.156.103:37050->172.20.198.213:11211: i/o timeout" level=error ts=2024-05-17T10:34:38.434170592Z caller=memcached.go:153 msg="Failed to get keys from memcached" err="read tcp 10.20.156.103:37048->172.20.198.213:11211: i/o timeout"
level=error ts=2024-05-17T10:36:38.334049743Z caller=memcached.go:236 msg="failed to put to memcached" name=parquet-footer|bloom|frontend-search err="server=172.20.198.213:11211: read tcp 10.20.156.103:39990->172.20.198.213:11211: i/o timeout" level=error ts=2024-05-17T10:36:38.334101886Z caller=memcached.go:236 msg="failed to put to memcached" name=parquet-footer|bloom|frontend-search err="server=172.20.198.213:11211: read tcp 10.20.156.103:36876->172.20.198.213:11211: i/o timeout"
But when tried to do telnet using service cluster ip to the port 11211 its able to connect
telnet 172.20.198.213 11211
Hence we are able to query traces but they run slow as they are not being cached in the memcached.
Need your help please
To Reproduce
Deploy tempo-distributed chart via helm deployment in K8s
Chart version - v1.9.9
App version - v2.4.1
Expected behavior
Timeouts shouldn't appear and the querier should be able to get/set keys from memcache
Environment:
Infrastructure: Kubernetes
Deployment tool: helm
Additional Context
Tempo configuration that gives timeout
Describe the bug We are new to tempo, and we recently deployed tempo via helm chart in k8s cluster. We use grafana to view traces. After the deployment we noticed that we are getting timeouts when the tempo querier component tries to get/set keys from memcached.
level=error ts=2024-05-17T10:34:38.433823747Z caller=memcached.go:153 msg="Failed to get keys from memcached" err="read tcp 10.20.156.103:37050->172.20.198.213:11211: i/o timeout" level=error ts=2024-05-17T10:34:38.434170592Z caller=memcached.go:153 msg="Failed to get keys from memcached" err="read tcp 10.20.156.103:37048->172.20.198.213:11211: i/o timeout"
level=error ts=2024-05-17T10:36:38.334049743Z caller=memcached.go:236 msg="failed to put to memcached" name=parquet-footer|bloom|frontend-search err="server=172.20.198.213:11211: read tcp 10.20.156.103:39990->172.20.198.213:11211: i/o timeout" level=error ts=2024-05-17T10:36:38.334101886Z caller=memcached.go:236 msg="failed to put to memcached" name=parquet-footer|bloom|frontend-search err="server=172.20.198.213:11211: read tcp 10.20.156.103:36876->172.20.198.213:11211: i/o timeout"
But when tried to do telnet using service cluster ip to the port 11211 its able to connect
telnet 172.20.198.213 11211
Hence we are able to query traces but they run slow as they are not being cached in the memcached. Need your help please
To Reproduce Deploy tempo-distributed chart via helm deployment in K8s Chart version - v1.9.9 App version - v2.4.1
Expected behavior Timeouts shouldn't appear and the querier should be able to get/set keys from memcache
Environment:
Additional Context Tempo configuration that gives timeout