Skip to content
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

Cannot connect to query-service via gRPC #1754

Closed
yurishkuro opened this issue Aug 22, 2019 · 0 comments · Fixed by #1758
Closed

Cannot connect to query-service via gRPC #1754

yurishkuro opened this issue Aug 22, 2019 · 0 comments · Fixed by #1758
Labels
bug help wanted Features that maintainers are willing to accept but do not have cycles to implement

Comments

@yurishkuro
Copy link
Member

yurishkuro commented Aug 22, 2019

Reported by @32leaves on Gitter.

Requirement - what kind of business use case are you trying to solve?

Programmatically retrieve traces via gRPC endpoint on all-in-one.

Problem - what in Jaeger blocks you from solving the requirement?

https://gist.github.com/32leaves/8d422784ad7cb105ff4b1a36e8726222

gRPC client cannot complete the handshake with the server.

Proposal - what do you suggest to solve the problem or improve the existing situation?

Looks like a bug. We should have a working example and a unit test.

Any open questions to address

At Uber we have an internal client library that works, but we're running gRPC server on a separate port from HTTP server, so the issue might be with the cmux.

@yurishkuro yurishkuro added bug help wanted Features that maintainers are willing to accept but do not have cycles to implement labels Aug 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug help wanted Features that maintainers are willing to accept but do not have cycles to implement
Projects
None yet
1 participant