You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Daren Wong (Jira)" <ji...@apache.org> on 2022/12/14 13:29:00 UTC

[jira] [Created] (FLINK-30418) Implement synchronous KinesisClient in EFO

Daren Wong created FLINK-30418:
----------------------------------

             Summary: 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
    Affects Versions: aws-connector-4.1.0
            Reporter: Daren Wong
             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)