[
https://issues.apache.org/jira/browse/FLINK-13249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885981#comment-16885981
]
Stefan Richter commented on FLINK-13249:
----------------------------------------
My tendency is also more towards having a well-specified executor, in
particular as the code is not just some stateless request.
I would have another suggestion that might get around the problem, so how about
changing:
{code}
void requestPartitionProducerState(
IntermediateDataSetID intermediateDataSetId,
ResultPartitionID resultPartitionId,
Consumer<? super ResponseHandle> responseConsumer);
{code}
and then do in `Task`
{code}
futurePartitionState.whenCompleteAsync(
(ExecutionState executionState, Throwable throwable) ->
{
responseConsumer.accept(new
PartitionProducerStateResponseHandle(executionState, throwable));
},
executor);
{code}
This would keep the control where execution happens in the task and we don't
need to pass down the executor. Wdyt?
> 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)
