You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/02/19 12:14:00 UTC
[jira] [Updated] (AMBARI-25137) SECONDARY_NAMENODE check failed
when calling rolling upgrade in the ambari managing multi-clusters
[ https://issues.apache.org/jira/browse/AMBARI-25137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated AMBARI-25137:
------------------------------------
Labels: pull-request-available (was: )
> SECONDARY_NAMENODE check failed when calling rolling upgrade in the ambari managing multi-clusters
> ----------------------------------------------------------------------------------------------------
>
> Key: AMBARI-25137
> URL: https://issues.apache.org/jira/browse/AMBARI-25137
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.7.0
> Reporter: yangqk
> Priority: Major
> Labels: pull-request-available
>
> If i create two clusters in a ambari ,one of them is HA mode, and another is nn and snn mode, i want to upgrade the HA cluster with rolling upgrade mode, the ambari server will reponse "
> The SNameNode component must be deleted from host:"
> I found the next code :
> {code:java}
> // Try another method to find references to SECONDARY_NAMENODE
> if (hosts.isEmpty()) {
> List<HostComponentStateEntity> allHostComponents = hostComponentStateDao.findAll();
> for(HostComponentStateEntity hc : allHostComponents) {
> if (hc.getServiceName().equalsIgnoreCase(HDFS_SERVICE_NAME) && hc.getComponentName().equalsIgnoreCase(SECONDARY_NAMENODE)) {
> hosts.add(hc.getHostName());
> }
> }
> }
> {code}
> it means this checker will find all hosts which has the snn component regardless of whether it belongs to this cluster.
> Maybe HostComponentStateDao should have a findByCluster method
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)