[jira] [Commented] (FLINK-34071) Deadlock in AWS Kinesis Data Streams AsyncSink connector

2024-04-30 Thread Aleksandr Pilipenko (Jira)
[ https://issues.apache.org/jira/browse/FLINK-34071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842275#comment-17842275 ] Aleksandr Pilipenko commented on FLINK-34071: - [~chalixar] for exception classification I

[jira] [Commented] (FLINK-34071) Deadlock in AWS Kinesis Data Streams AsyncSink connector

2024-04-29 Thread Ahmed Hamdy (Jira)
[ https://issues.apache.org/jira/browse/FLINK-34071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842153#comment-17842153 ] Ahmed Hamdy commented on FLINK-34071: - Additionally the timeout configuration setup is addressed in

[jira] [Commented] (FLINK-34071) Deadlock in AWS Kinesis Data Streams AsyncSink connector

2024-04-29 Thread Ahmed Hamdy (Jira)
[ https://issues.apache.org/jira/browse/FLINK-34071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842152#comment-17842152 ] Ahmed Hamdy commented on FLINK-34071: - [~a.pilipenko] Could we follow up and update Exception

[jira] [Commented] (FLINK-34071) Deadlock in AWS Kinesis Data Streams AsyncSink connector

2024-04-29 Thread Aleksandr Pilipenko (Jira)
[ https://issues.apache.org/jira/browse/FLINK-34071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842055#comment-17842055 ] Aleksandr Pilipenko commented on FLINK-34071: - We found that one of the causes of this -

[jira] [Commented] (FLINK-34071) Deadlock in AWS Kinesis Data Streams AsyncSink connector

2024-01-15 Thread Hong Liang Teoh (Jira)
[ https://issues.apache.org/jira/browse/FLINK-34071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17806733#comment-17806733 ] Hong Liang Teoh commented on FLINK-34071: - As discussed offline, wonder if we can add a timeout