-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set wait for ready in Jaeger gRPC exporter #899
Set wait for ready in Jaeger gRPC exporter #899
Conversation
exporter/jaegerexporter/exporter.go
Outdated
@@ -80,7 +80,7 @@ func (s *protoGRPCSender) pushTraceData( | |||
for _, batch := range batches { | |||
_, err = s.client.PostSpans( | |||
ctx, | |||
&jaegerproto.PostSpansRequest{Batch: *batch}) | |||
&jaegerproto.PostSpansRequest{Batch: *batch}, grpc.WaitForReady(true)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This has to be configurable otherwise tests are failing.
Any objections on adding to the main gRPC config?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would like to read the documentation before saying anything. Will do that in 30 mins and confirm
|
Signed-off-by: Pavol Loffay <ploffay@redhat.com>
b9b2f78
to
b5fbaab
Compare
* Make wait for ready configurable in gRPC exporters Signed-off-by: Pavol Loffay <ploffay@redhat.com> * Fix Signed-off-by: Pavol Loffay <ploffay@redhat.com>
* Adds Database-specific semantic attributes. * Add CHANGELOG Co-authored-by: Tyler Yahn <MrAlias@users.noreply.github.com>
Description:
gRPC can drop a couple of initial RPCs at the beginning of the connection. Wait for ready should prevent it.
Some resources:
This feature is needed in Jaeger to make crossdock tests pass. Sometimes Jaeger exporter drops first batches that is causing test failures. I have tested this PR in jaegertracing/jaeger#2211
Link to tracking Issue:
Testing: < Describe what testing was performed and which tests were added.>
Documentation: < Describe the documentation added.>