[
https://issues.apache.org/jira/browse/FLINK-16017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17044298#comment-17044298
]
Zhu Zhu commented on FLINK-16017:
---------------------------------
Yes region creation is now invoked twice, one from
RegionPartitionReleaseStrategy and the other from
RestartPipelinedRegionFailoverStrategy. Removing
AdaptedRestartPipelinedRegionStrategyNG does not reduce the invocation number.
However, in 1.11 we will do region based scheduling and will make regions
higher level concepts, that means regions would then be built and then passed
into release strategy and failover strategy. That would naturally fix this
issue.
> Improve attachJobGraph Performance
> ----------------------------------
>
> Key: FLINK-16017
> URL: https://issues.apache.org/jira/browse/FLINK-16017
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.10.0
> Reporter: Jiayi Liao
> Priority: Major
>
> Currently {{RegionPartitionReleaseStrategy}} and
> {{AdaptedRestartPipelinedRegionStrategyNG}} both need to compute distinct
> pipelined regions, which affects the performance due to the duplicate
> calculating.
> The best idea that comes to my mind so far is calculating distinct pipelined
> regions in {{DefaultExecutionTopology}} so that we can remove the duplicate
> calculating.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
