You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Alexey Romanenko (Jira)" <ji...@apache.org> on 2021/12/24 14:27:00 UTC
[jira] [Commented] (BEAM-13509) SQS reader uses shared client instance without coordinating shutdown (AWS SDK v2)
[ https://issues.apache.org/jira/browse/BEAM-13509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465036#comment-17465036 ]
Alexey Romanenko commented on BEAM-13509:
-----------------------------------------
Could you add some details about "_without appropriate coordination when to close clients._" ? What is expected behaviour there?
I can be wrong but client sharing among the readers (memoization) looks like a premature optimization here and can be avoided at all, so every reader will use own client as usual. Am I wrong?
> SQS reader uses shared client instance without coordinating shutdown (AWS SDK v2)
> ---------------------------------------------------------------------------------
>
> Key: BEAM-13509
> URL: https://issues.apache.org/jira/browse/BEAM-13509
> Project: Beam
> Issue Type: Bug
> Components: io-java-aws
> Reporter: Moritz Mack
> Assignee: Moritz Mack
> Priority: P2
> Labels: SQS, aws-sdk-v2
>
> The SQS client may be shared across readers of the same source instance without appropriate coordination when to close clients.
> This affects the direct runner, I'm not sure if other runners behave in a similar way (cc [~aromanenko] ).
> Investigate if this is also an issue in SDK v1.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)