[
https://issues.apache.org/jira/browse/FLINK-6227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16774949#comment-16774949
]
zhijiang commented on FLINK-6227:
---------------------------------
I think this task seems a bit complicated for the beginner. First you should be
familiar with the network stack in order to know which exceptions should be
wrapped into {{DataConsumptionException}}.
I am not sure the latest state of failover strategy on JobMaster side, and how
this {{DataConsumptionException}} is used for determining whether the upstream
should be restarted or not. So it is better to trace the related logics before
starting it.
If you are interested in it, welcome to have a try! :)
> Introduce the DataConsumptionException for downstream task failure
> ------------------------------------------------------------------
>
> Key: FLINK-6227
> URL: https://issues.apache.org/jira/browse/FLINK-6227
> Project: Flink
> Issue Type: Sub-task
> Components: Network
> Reporter: zhijiang
> Priority: Minor
>
> It is part of FLIP-1.
> We define a new special exception to indicate the downstream task failure in
> consuming upstream data.
> The {{JobManager}} will receive and consider this special exception to
> calculate the minimum connected sub-graph which is called {{FailoverRegion}}.
> So the {{DataConsumptionException}} should contain {{ResultPartitionID}}
> information for {{JobMaster}} tracking upstream executions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
