[jira] [Comment Edited] (HIVE-17904) handle internal Tez AM restart in registry and WM

["Sergey Shelukhin (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HIVE-17904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16245108#comment-16245108 ] 

Sergey Shelukhin edited comment on HIVE-17904 at 11/9/17 2:09 AM:
------------------------------------------------------------------

Actually I guess this will also need to go thru the WM thread (or maybe the  session can update itself bypassing the WM thread), because we need to re-send allocation to the newly restarted AM. I will either update the patch later or file a JIRA


was (Author: sershe):
Actually I guess this will also need to go thru the WM thread (or maybe the  session can update itself bypassing the WM thread), because we need to re-send allocation to the newly restarted AM.

> handle internal Tez AM restart in registry and WM
> -------------------------------------------------
>
>                 Key: HIVE-17904
>                 URL: https://issues.apache.org/jira/browse/HIVE-17904
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>         Attachments: HIVE-17904.01.patch, HIVE-17904.patch, HIVE-17904.patch
>
>
> After the plan update patch is committed. The current code doesn't account very well for it; registry may have races, and an event needs to be added to WM when some AM resets, at least to make sure we discard the update errors that pertain to the old AM. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)