We sometimes see `grpc: failed to set
# spicedbt
tokongs
02/27/2025, 3:29 PMWe sometimes see
grpc: failed to set send compressor: transport: set send compressor called after headers sent or stream donedispatch.v1.DispatchService/DispatchChecky
yetitwo
02/27/2025, 3:42 PMi haven't seen that before. i don't think we're manually managing compressors on our internal API clients, and it sounds like it's retrying or otherwise dealing with it. I think this might be an implementation detail of the grpc-go client?
v
vroldanbet
02/27/2025, 3:52 PMspicedb uses snappy compression in the dispatch API
vroldanbet
02/27/2025, 3:52 PMwhat version are you running?
e
eric524
02/27/2025, 9:22 PMI'm seeing same issues as well. I am using 1.39.1
v
vroldanbet
02/28/2025, 9:40 AMbut where do you see this, in the spicedb logs? or is it returned as an error to the client?
t
tokongs
02/28/2025, 1:31 PMIt's form an otel span,
dispatch.v1.DispatchService/DispatchCheckv
vroldanbet
02/28/2025, 1:52 PMyou are saying that is shows in an otel span?
v
vroldanbet
02/28/2025, 1:58 PMinteresting
vroldanbet
02/28/2025, 1:58 PMmind opening an issue with the image?
vroldanbet
02/28/2025, 1:58 PMdispatch requests are canceled often, which shows as an error
vroldanbet
02/28/2025, 1:59 PMthat's part of how SpiceDB works - I wish there was a way to not show those as failed in the trace
vroldanbet
02/28/2025, 1:59 PMbut that is new
t
tokongs
02/28/2025, 2:05 PMv
vroldanbet
02/28/2025, 2:47 PMthank you!
8 Views