You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2017/08/09 22:41:00 UTC
[jira] [Commented] (HIVE-17281) LLAP external client not properly
handling KILLED notification that occurs when a fragment is rejected
[ https://issues.apache.org/jira/browse/HIVE-17281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16120769#comment-16120769 ]
Sergey Shelukhin commented on HIVE-17281:
-----------------------------------------
+1 on the logic. I'm assuming no extra synchronization is necessary w.r.t. state checks and changes.
> LLAP external client not properly handling KILLED notification that occurs when a fragment is rejected
> ------------------------------------------------------------------------------------------------------
>
> Key: HIVE-17281
> URL: https://issues.apache.org/jira/browse/HIVE-17281
> Project: Hive
> Issue Type: Bug
> Components: llap
> Reporter: Jason Dere
> Assignee: Jason Dere
> Attachments: HIVE-17281.1.patch
>
>
> When LLAP fragment submission is rejected, the external client receives both REJECTED and KILLED notifications for the fragment. The KILLED notification is being treated as an error, which prevents the retry logic from resubmitting the fragment. This needs to be fixed in the client logic.
> {noformat}
> 17/08/02 04:36:16 INFO LlapBaseInputFormat: Registered id: attempt_2519876382789748565_0005_0_00_000021_0
> 17/08/02 04:36:16 INFO LlapTaskUmbilicalExternalClient: Fragment: attempt_2519876382789748565_0005_0_00_000021_0 rejected. Server Busy.
> 17/08/02 04:36:16 ERROR LlapTaskUmbilicalExternalClient: Task killed - attempt_2519876382789748565_0005_0_00_000021_0
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)