[jira] [Commented] (AMBARI-22175) Host check operation is being performed on all hosts during host add
[ https://issues.apache.org/jira/browse/AMBARI-22175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284283#comment-16284283 ] Swapan Shridhar commented on AMBARI-22175: -- Moved it to 3.0 as I am started the 2.6.1 release process. > Host check operation is being performed on all hosts during host add > > > Key: AMBARI-22175 > URL: https://issues.apache.org/jira/browse/AMBARI-22175 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.1 >Reporter: amarnath reddy pappu >Priority: Critical > Fix For: 3.0.0 > > > Steps to reproduce: > 1. Have a cluster with 2/3 hosts > 2. now try to add a new host from UI > 3. Ambari initiates host check for all the hosts in the cluster instead of > doing it for new host alone. if there is any issues with other hosts then > host add will get hung and will not be able to proceed further. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22175) Host check operation is being performed on all hosts during host add
[ https://issues.apache.org/jira/browse/AMBARI-22175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214619#comment-16214619 ] Swapan Shridhar commented on AMBARI-22175: -- Moving it out of Ambari 2.6 to 2.6.1, as I have to start the release process for Ambari 2.6. > Host check operation is being performed on all hosts during host add > > > Key: AMBARI-22175 > URL: https://issues.apache.org/jira/browse/AMBARI-22175 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.1 >Reporter: amarnath reddy pappu >Priority: Critical > Fix For: 2.6.1 > > > Steps to reproduce: > 1. Have a cluster with 2/3 hosts > 2. now try to add a new host from UI > 3. Ambari initiates host check for all the hosts in the cluster instead of > doing it for new host alone. if there is any issues with other hosts then > host add will get hung and will not be able to proceed further. -- This message was sent by Atlassian JIRA (v6.4.14#64029)