You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Prasanth Jayachandran (JIRA)" <ji...@apache.org> on 2017/12/06 07:15:00 UTC
[jira] [Commented] (HIVE-18078) WM getSession needs some retry
logic
[ https://issues.apache.org/jira/browse/HIVE-18078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16279770#comment-16279770 ]
Prasanth Jayachandran commented on HIVE-18078:
----------------------------------------------
nit in RB. looks good otherwise, +1 pending tests.
> WM getSession needs some retry logic
> ------------------------------------
>
> Key: HIVE-18078
> URL: https://issues.apache.org/jira/browse/HIVE-18078
> Project: Hive
> Issue Type: Sub-task
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Attachments: HIVE-18078.only.patch, HIVE-18078.patch
>
>
> When we get a bad session (e.g. no registry info because AM has gone catatonic), the failure by the timeout future fails the getSession call.
> The retry model in TezTask is that it would get a session (which in original model can be completely unusable, but we still get the object), and then retry (reopen) if it's a lemon. If the reopen fails, we fail.
> getSession is not covered by this retry scheme, and should thus do its own retries (or the retry logic needs to be changed)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)