[
https://issues.apache.org/jira/browse/BEAM-12356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17357109#comment-17357109
]
Per Böckman commented on BEAM-12356:
------------------------------------
Reported the [same issue
yesterday|https://issues.apache.org/jira/browse/BEAM-12365?focusedCommentId=17356620&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17356620]
and it blocks us from upgrading to beam 2.29.0 / 2.30.0.
We cannot simply ignore all errors being logged as that would mean turning off
all production alerts for our dataflow pipelines.
One workaround might be to suppress all ERROR logs from
io.grpc.internal.ManagedChannelOrphanWrapper but that would hide other issues
from that component so it's not an ideal solution. Any other suggestions?
> BigQueryWriteClient in DatasetServiceImpl is not closed, which causes
> "ManagedChannel allocation site" exceptions
> -----------------------------------------------------------------------------------------------------------------
>
> Key: BEAM-12356
> URL: https://issues.apache.org/jira/browse/BEAM-12356
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp
> Affects Versions: 2.29.0
> Reporter: Minbo Bae
> Assignee: Reuven Lax
> Priority: P2
> Attachments: bigquery_grpc.log
>
>
> [BigQueryWriteClient|https://github.com/apache/beam/blob/v2.29.0/sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/bigquery/BigQueryServicesImpl.java#L461]
> 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
> [https://github.com/googleapis/java-bigtable-hbase/issues/2658]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
