[
https://issues.apache.org/jira/browse/FLINK-10914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16694152#comment-16694152
]
TisonKun commented on FLINK-10914:
----------------------------------
[~till.rohrmann] [~StephanEwen] do you mean, as your conversation above, there
is some on-going effort to change the concurrency model of the execution graph,
and so that we delay this issue until that has been done and see how to improve
this test stability?
If so, I'd like to see if I can help with the work that discuss/implement the
new concurrency model(single threaded dispatcher).
> Prefer notifying status changed to waiting and checking in ExecutionGraph
> tests
> -------------------------------------------------------------------------------
>
> Key: FLINK-10914
> URL: https://issues.apache.org/jira/browse/FLINK-10914
> Project: Flink
> Issue Type: Improvement
> Components: Tests
> Affects Versions: 1.8.0
> Reporter: TisonKun
> Assignee: TisonKun
> Priority: Major
> Fix For: 1.8.0
>
>
> Currently there are several tests of {{ExecutionGraph}} based on
> {{ExecutionGraphTestUtils#waitUntilJobStatus}} and
> {{ExecutionGraphTestUtils#waitUntilExecution(Vertex)State}}. I notice that we
> have {{JobStatusListener}} s and {{ExecutionStatusListener}} s registered on
> a {{ExecutionGraph}}. It is possible to replace the waiting version with a
> notifying version, which is with less cpu workload and more reliable(the
> waiting version might miss some very quick status/state changes).
> What do you think [~till.rohrmann] [~Zentol]?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
