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

Posted to issues@ambari.apache.org by "Prasanth Jayachandran (JIRA)" <ji...@apache.org> on 2017/06/15 09:10:00 UTC

[jira] [Created] (AMBARI-21253) On RM restart, LLAP app starts up after many failed application attempts

Prasanth Jayachandran created AMBARI-21253:
----------------------------------------------

             Summary: On RM restart, LLAP app starts up after many failed application attempts
                 Key: AMBARI-21253
                 URL: https://issues.apache.org/jira/browse/AMBARI-21253
             Project: Ambari
          Issue Type: Bug
          Components:  HiveServer2, Metastore, and Client Heap Sizes to Smart Configs
            Reporter: Prasanth Jayachandran


LLAP concurrency is set to 1. On LLAP + related components restart, app ID of llap0 is application_xxx_0005. There are 3 failed application attempts. Was expecting llap0 to be _001 application followed by tez AM.
[~sseth] mentioned he has seen llap0 itself being restarted.
Need to analyze why some AM/llap attempts are failing/launching.



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