-
Notifications
You must be signed in to change notification settings - Fork 85
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
BigQuery Storage Write API: Callback doesnt return and blocks indefinitely during appendrows #1727
Comments
Which thread gets parked? It is the Future callback, or done callback? Could you try a sync mode which is directly call future.get to see if that can succeed? |
Thank you for your reply. The done callback thread is the one that gets parked . I will try to directly call future.get().Actually I am facing a similar issue when I am trying to create a WriteStream. The thread just gets parked and the program hangs. This is a sample thread dump :-
|
Maybe try set your server's default executor or something? Most likely no executor is executing the threads: |
Apologies for the late reply , but yes I tried to set a default executor and the issue still seems to persist. |
The thread actually keeps waiting for the a response from the object 'CallbackChainRetryingFuture' and the program hangs from then on as it does not receive any response. |
When I try to execute this piece of code in a standalone tool, it works fine. But when I try to integrate it with another project the thread gets parked,blocks indefinitely and the program just hangs. Eventually i get the exception Caused by: java.lang.RuntimeException: io.grpc.StatusRuntimeException: CANCELLED: Timeout waiting for DoneCallback. . Could someone please help.
This is the grpc stack trace.
Caused by: io.grpc.StatusRuntimeException: CANCELLED: Timeout waiting for DoneCallback.
at com.google.cloud.bigquery.storage.v1.StreamWriter.waitForDoneCallback(StreamWriter.java:540)
at com.google.cloud.bigquery.storage.v1.StreamWriter.appendLoop(StreamWriter.java:493)
... 3 more
Version used :
The text was updated successfully, but these errors were encountered: