[
https://issues.apache.org/jira/browse/FLINK-14480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-14480:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Sort out exception supression during snapshotting for non-running tasks.
> ------------------------------------------------------------------------
>
> Key: FLINK-14480
> URL: https://issues.apache.org/jira/browse/FLINK-14480
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Checkpointing
> Affects Versions: 1.10.0
> Reporter: Arvid Heise
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> Following-up on FLINK-14370.
> As [~becket_qin] wrote: "The cause [of the unstable test] was that when all
> the records are processed before a snapshot was taken, the records that could
> not be sent out trigger the snapshot to fail. That snapshot failure will not
> cause the job to exit. However, all the records in the KafkaProducer are
> already expired after the snapshot failure. So when the producer closes,
> there will be no more exception thrown. Thus the job finished successfully.
> It looks that the expected behavior from connector is to report exception in
> {{close()}} method as long as there was a record that could not be sent. On
> the other hand, exception thrown from
> {{CheckpointedFunction.snapshotState()}} might be ignored. Not sure if this
> is reasonable, but this expectation is not super clear from the connector
> implementation's perspective.
> In terms of immediate fix, [[email protected]] proposes to always throw
> exception as long as there has been a record sending failure. I agree that is
> the right fix per current expected behavior on the connectors."
> [~kkl0u], [~pnowojski] any other idea on how to resolve it?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
