You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Siddharth Seth (JIRA)" <ji...@apache.org> on 2017/03/02 23:41:45 UTC

[jira] [Updated] (HIVE-16094) queued containers may timeout if they don't get to run for a long time

     [ https://issues.apache.org/jira/browse/HIVE-16094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Siddharth Seth updated HIVE-16094:
----------------------------------
    Status: Patch Available  (was: Open)

> queued containers may timeout if they don't get to run for a long time
> ----------------------------------------------------------------------
>
>                 Key: HIVE-16094
>                 URL: https://issues.apache.org/jira/browse/HIVE-16094
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 2.2.0
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>            Priority: Critical
>         Attachments: HIVE-16094.01.patch
>
>
> I believe this happened after HIVE-15958 - since we end up keeping amNodeInfo in knownAppMaters, and that can result in the callable not being scheduled on new task registration.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)