You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/10/26 06:21:00 UTC
[jira] [Updated] (HUDI-5090) throw runtime Exception when flink streming job checkpoint abort
[ https://issues.apache.org/jira/browse/HUDI-5090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HUDI-5090:
---------------------------------
Labels: pull-request-available (was: )
> throw runtime Exception when flink streming job checkpoint abort
> ----------------------------------------------------------------
>
> Key: HUDI-5090
> URL: https://issues.apache.org/jira/browse/HUDI-5090
> Project: Apache Hudi
> Issue Type: Bug
> Components: flink
> Reporter: chenfengLiu
> Assignee: chenfengLiu
> Priority: Major
> Labels: pull-request-available
>
> When write task in a Flink job want to flush data, there is a condition that listened a new instant which have been start. If there is no new instant, the TM will wait for timeout.
> We can see the code at [https://github.com/apache/hudi/blob/master/hudi-flink-datasource/hudi-flink/src/main/java/org/apache/hudi/sink/common/AbstractStreamWriteFunction.java#L252.]
> Now there is a case that when the JM start new instant fail, JM won't retry this work. So how all the write tasks will hang.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)