Hello, we noticed that our SpiceDB OTEL traces are...
# spicedb
u
Hello, we noticed that our SpiceDB OTEL traces are full of errors like
context canceled
or
request canceled: request canceled
from
DispatchCheck dispatch.v1.DispatchService
This is the case even for pretty fast and succeful requests (like the example attached) but we can see a clear correlation between the number of such errors and the latency spikes in our SpiceDB setup. Any advice on what the problem can be here would be highly appreciated. We're running 2 SpiceDB pods with
cpu: 1500m
each. Should we maybe adjust some default concurrency settings or consider adding more CPUs to our pods or is there anything else that we could do?