[ 
https://issues.apache.org/jira/browse/FLINK-30418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17647106#comment-17647106
 ] 

Danny Cranmer commented on FLINK-30418:
---------------------------------------

Thanks Daren, have assigned to you

> Implement synchronous KinesisClient in EFO
> ------------------------------------------
>
>                 Key: FLINK-30418
>                 URL: https://issues.apache.org/jira/browse/FLINK-30418
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / AWS
>            Reporter: Daren Wong
>            Assignee: Daren Wong
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: aws-connector-4.1.0
>
>
> Use synchronous KinesisClient for consumer registration/de-registration.
> h3. 
> Why?
> This is because current async client can cause the following RuntimeException 
> when app parallelism is high.
> {quote}Unable to execute HTTP request: The channel was closed before the 
> protocol could be determined.
> {quote}
> In addition, it can also cause deadlock situation as described in 
> https://issues.apache.org/jira/browse/FLINK-30304



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to