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

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

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

Siddharth Seth created HIVE-16094:
-------------------------------------

             Summary: 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


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)