[
https://issues.apache.org/jira/browse/FLINK-13249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885059#comment-16885059
]
Stefan Richter commented on FLINK-13249:
----------------------------------------
[~till.rohrmann] alright, I think then we have a consensus on how to approach
this. I think the last remaining question is whether or not we actually require
to pass in the task's executor or simply use the common pool. Option one
obviously has the advantage that it integrates with how execution is supposed
to happen and with with the task lifecycle, disadvantage is that it seems like
we would need to pass down the executor from quiet far way. Option 2 would be
simpler if we agree that there is no requirement that this has to run through
the particular executor.
> Distributed Jepsen test fails with blocked TaskExecutor
> -------------------------------------------------------
>
> Key: FLINK-13249
> URL: https://issues.apache.org/jira/browse/FLINK-13249
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Network
> Affects Versions: 1.9.0
> Reporter: Till Rohrmann
> Assignee: Stefan Richter
> Priority: Blocker
> Labels: test-stability
> Fix For: 1.9.0
>
> Attachments: jstack_25661_YarnTaskExecutorRunner
>
>
> The distributed Jepsen test which kills {{JobMasters}} started to fail
> recently. From a first glance, it looks as if the {{TaskExecutor's}} main
> thread is blocked by some operation. Further investigation is required.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
