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

Posted to issues@ambari.apache.org by "Vivek Sharma (JIRA)" <ji...@apache.org> on 2018/06/26 07:17:00 UTC

[jira] [Updated] (AMBARI-23564) Start All Services Fails after ambari upgrade as Livy(Spark2) tries to access Namenode which is not yet started.

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

Vivek Sharma updated AMBARI-23564:
----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

> Start All Services Fails after ambari upgrade as Livy(Spark2) tries to access Namenode which is not yet started.
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-23564
>                 URL: https://issues.apache.org/jira/browse/AMBARI-23564
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Jasmeen Kaur
>            Assignee: Vivek Sharma
>            Priority: Blocker
>              Labels: pull-request-available
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> STR
> 1) Install Ambari-2.6.0.0-267
> 2) Stop All Services 
> 3) Upgrade Ambari from 2.6.0.0-267 to 2.7.0.0-292
> 4) Upgrade Non Stack Services (Smartsense , Ambari Infra , Logsearch)
> 5) try to start all services.
> Cause - Livy for Spark2 Server Start operation tries to access namenode whereas Namenode start hasn't happened yet. Looks to be some issue with RCO sequence of operations. Hence all other operations are aborted.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)