-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
BigQueryWriteClient in DatasetServiceImpl is not closed, which causes "ManagedChannel allocation site" exceptions #20970
Comments
May I know if there is an update for this? Thanks |
@databius (and anyone else who encounters this): Could you share stacktraces where this happened and the Beam verision you were using? That will help us pinpoint the client that is not being cleaned up. FYI @johnjcasey - this comes up a lot. Some of the more recent stacktraces posted in BEAM-12356 may not have been tracked down. |
Hi all I think that I got this error on apache beam 2.41, java 11 this is my stack trace, it happens during reading phase
hope to have reported all valuable info |
…dSourceAdapter.Reader#init() in Dataflow worker (#28548)
BigQueryWriteClient in DatasetServiceImpl (added at https://github.com/apache/beam/pull/14309)) is not closed. This causes the error logs in gRPC orphan channel clean up. See "bigquery_grpc.log" in attachments which is extracted from GCP Dataflow. I don't think this issue affect pipeline runs except the error logs, but could you take a look at that?
A similar issue is reported for
CloudBigtableIO
at googleapis/java-bigtable-hbase#2658Imported from Jira BEAM-12356. Original Jira may contain additional context.
Reported by: baeminbo.
The text was updated successfully, but these errors were encountered: