[
https://issues.apache.org/jira/browse/FLINK-12203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann resolved FLINK-12203.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.9.0
Fixed via b62db93bf63cb3bb34dd03d611a779d9e3fc61ac
> Refactor ResultPartitionManager to break tie with Task
> ------------------------------------------------------
>
> Key: FLINK-12203
> URL: https://issues.apache.org/jira/browse/FLINK-12203
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Network
> Reporter: Andrey Zagrebin
> Assignee: Andrey Zagrebin
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> At the moment, we have ResultPartitionManager.releasePartitionsProducedBy
> which uses indexing by task in network environment. These methods are
> eventually used only by Task which already knows its partitions so Task can
> use ResultPartition.fail(cause) and TaskExecutor.failPartition could directly
> use NetworkEnviroment.releasePartitions(Collection<ResultPartitionID>). This
> also requires that JM Execution sends produced partition ids instead of just
> ExecutionAttemptID.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
