You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Well, I got past my other issue where I was trying to send messages over the NGINX Ingress default max message size (see related question #3196) but unfortunately, I seem to have hit another max message size limit that seems to be in the Collector itself.
On the Jaeger Client side, I set my max span size to over 4mb (a value > 410241024 which is the default max span size and also the default max message size for gRPC apparently). This allows me to attempt to send a larger Span to the gRPC Collector but when I turn on gRPC debugging, I see the following error:
I've been digging through the gRPC documentation and the Jaeger Collector CLI options but I have not been able to find any way to set the max gRPC message size options (one of these two it seems but likely the second one):
grpc.max_send_message_length
grpc.max_receive_message_length
Is there some way that the Jaeger Collector allows me to set these max message sizes?
I don't know Go but from what I can tell in the Go gRPC library, one can set the Max Received Message Size (grpc.max_receive_message_length) by doing something like this (maybe in the grpc.go -> StartGRPCServer() function:
// StartGRPCServer based on the given parametersfuncStartGRPCServer(params*GRPCServerParams) (*grpc.Server, error) {
varserver*grpc.ServervargrpcOpts []grpc.ServerOptiongrpcOpts=append(grpcOpts, grpc.MaxRecvMsgSize(10*1024*1024))
That StartGRPCServer function gets called by collector.go -> Start() so that's my best guess and I also don't see MaxCallRecvMsgSize referenced anywhere else in the Jaeger code so I'm guessing it is just not a supported setting right now. I'd love it if someone could confirm!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Well, I got past my other issue where I was trying to send messages over the NGINX Ingress default max message size (see related question #3196) but unfortunately, I seem to have hit another max message size limit that seems to be in the Collector itself.
On the Jaeger Client side, I set my max span size to over 4mb (a value > 410241024 which is the default max span size and also the default max message size for gRPC apparently). This allows me to attempt to send a larger Span to the gRPC Collector but when I turn on gRPC debugging, I see the following error:
This was confounding me for a while but then I realized I was seeing this error in my Ingress Controller on my K3S cluster (NGINX):
From digging around online, it seems like his might be due to the upstream service. However, I don't see anything in my Collector pod logs even though I have the log-level set to debug:
I've been digging through the gRPC documentation and the Jaeger Collector CLI options but I have not been able to find any way to set the max gRPC message size options (one of these two it seems but likely the second one):
grpc.max_send_message_length
grpc.max_receive_message_length
Is there some way that the Jaeger Collector allows me to set these max message sizes?
I don't know Go but from what I can tell in the Go gRPC library, one can set the Max Received Message Size (
grpc.max_receive_message_length
) by doing something like this (maybe in thegrpc.go -> StartGRPCServer()
function:That
StartGRPCServer
function gets called bycollector.go -> Start()
so that's my best guess and I also don't seeMaxCallRecvMsgSize
referenced anywhere else in the Jaeger code so I'm guessing it is just not a supported setting right now. I'd love it if someone could confirm!I created an Issue (Bug) for this: gRPC Collector Does Not Support Configurable Max Message Size #3210
Beta Was this translation helpful? Give feedback.
All reactions