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

Fix tcnative loading failure mode so that it throws an exception immediately instead of waiting until timeout (DEADLINE_EXCEEDED) #2109

Closed
garrettjonesgoogle opened this issue Jun 2, 2017 · 1 comment
Assignees
Labels
priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. status: blocked Resolving the issue is dependent on other work. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@garrettjonesgoogle
Copy link
Member

This is a tracking issue for the root cause in grpc: grpc/grpc-java#2599

@garrettjonesgoogle garrettjonesgoogle added priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. status: blocked Resolving the issue is dependent on other work. labels Jun 2, 2017
@garrettjonesgoogle garrettjonesgoogle changed the title Fix tcnative loading failure mode to throw exception immediately instead of waiting until timeout (DEADLINE_EXCEEDED) Fix tcnative loading failure mode so that it throws an exception immediately instead of waiting until timeout (DEADLINE_EXCEEDED) Jun 2, 2017
@garrettjonesgoogle
Copy link
Member Author

This was fixed with the upgrade to grpc 1.4 in google-cloud-java 0.20.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. status: blocked Resolving the issue is dependent on other work. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests

1 participant