[
https://issues.apache.org/jira/browse/HUDI-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17378949#comment-17378949
]
Danny Chen commented on HUDI-2162:
----------------------------------
You should set up the timeout correctly.
> Instant is null cause flushBuffer failed in casual
> --------------------------------------------------
>
> Key: HUDI-2162
> URL: https://issues.apache.org/jira/browse/HUDI-2162
> Project: Apache Hudi
> Issue Type: Bug
> Components: Flink Integration
> Reporter: zhangminglei
> Assignee: zhangminglei
> Priority: Blocker
>
> Since commit Instant and getting Instant are asynchronous , and thus instant
> is null the default waiting time is 0 must greater than ckpTimeout would
> cause Exception belows as shown.
> WRITE_COMMIT_ACK_TIMEOUT is for internal usage. so it is not suitable for
> java api user under exactly once, This kind of usage is too weak under the
> context.
> Timeout(0ms) while waiting for instant null to commit
> at
> org.apache.hudi.sink.StreamWriteFunction.instantToWrite(StreamWriteFunction.java:597)
> at
> org.apache.hudi.sink.StreamWriteFunction.flushBucket(StreamWriteFunction.java:618)
> at
> org.apache.hudi.sink.StreamWriteFunction.bufferRecord(StreamWriteFunction.java:554)
> at
> org.apache.hudi.sink.StreamWriteFunction.processElement(StreamWriteFunction.java:236)
> at
> org.apache.flink.streaming.api.operators.ProcessOperator.processElement(ProcessOperator.java:66)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
