[jira] [Updated] (AMBARI-23700) Stack scripts should only try to reach corresponding Namenode pair in the context rather than all NNs

["Siddharth Wagle (JIRA)" <ji...@apache.org>]

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

Siddharth Wagle updated AMBARI-23700:
-------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

> Stack scripts should only try to reach corresponding Namenode pair in the context rather than all NNs
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-23700
>                 URL: https://issues.apache.org/jira/browse/AMBARI-23700
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.7.0
>
>         Attachments: AMBARI-23700.patch
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> A good example is when we start up a specific Namenode, say NN1. In that case,
> we try to get the HAState of all the NNs (even NN3 and NN4) to find out the
> active namenode. This is not really needed since starting up NN1 should not
> care about NN3 and NN4's state.
> I see usages in following places.
>   * ambari-common/src/main/python/resource_management/libraries/providers/hdfs_resource.py
>   * ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode_ha_state.py
>   * ambari-common/src/main/python/resource_management/libraries/functions/namenode_ha_utils.py
> Some of the above might not need any change.



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