[BEAM-12356] Cache and shutdown BigQuery services#14949
Conversation
7bb6951 to
244a0cf
Compare
|
Run Java PreCommit |
|
I patched this cl and am still seeing some of the following, though much less than without this change. Is this expected to fix all of these logs? From "~ exception: |
|
@scwhittle can you try again? |
|
Still seems to be happening, I also added logging to see if the 60 seconds was just not enough and that didn't seem to be the case. |
|
@scwhittle I'm going to merge this PR, as it seems to remove most of the logs. We can investigate the rest separately; Beam will still create many individual DoFns, so it's possible that we should be caching things at a higher level. |
|
Are we planning to cherry pick this into Beam 2.31.0? /cc @apilloud |
* Reader.close(): fixes googleapis#2658 where original fix googleapis#2782 was rolled back by googleapis#2871 and googleapis#2873. As we don’t use “session” here anymore, I believe we should close “connection” here. * AbstractCloudBigtableTableDoFn.tearDown(): If an exception happened in ProcessElement, FinishBundle is not executed. We should clean up resources in TearDown. You can see the similar code with BigQueryIO apache/beam#14949.
No description provided.