[
https://issues.apache.org/jira/browse/DRILL-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156320#comment-16156320
]
ASF GitHub Bot commented on DRILL-3449:
---------------------------------------
GitHub user vrozov opened a pull request:
https://github.com/apache/drill/pull/934
DRILL-3449 When Foreman node dies, the FragmentExecutor still tries to send
status updates to Foreman
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vrozov/drill DRILL-3449
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/drill/pull/934.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #934
----
commit 06f15eeaf34c610fce0e3a62ae635c10f9885608
Author: Vlad Rozov <[email protected]>
Date: 2017-09-07T01:29:02Z
DRILL-3449 When Foreman node dies, the FragmentExecutor still tries to send
status updates to Foreman
----
> When Foreman node dies, the FragmentExecutor still tries to send status
> updates to Foreman
> ------------------------------------------------------------------------------------------
>
> Key: DRILL-3449
> URL: https://issues.apache.org/jira/browse/DRILL-3449
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Flow
> Reporter: Sudheesh Katkam
> Assignee: Vlad Rozov
> Priority: Minor
> Fix For: Future
>
>
> FragmentExecutor.FragmentDrillbitStatusListener discovers that the Foreman
> died and cancels the fragment which tries to update the Foreman with new
> CANCELLATION_REQUESTED status. This fails at RPC level. However, this error
> is not logged nor is it thrown. This just silently happens.
> + The fragment moves to CANCELED state, which is also reported to the Foreman
> and this also fails.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
