[jira] [Commented] (AMBARI-16028) Namenode marked as INITIAL standby could potentially never start if other namenode is down

[ https://issues.apache.org/jira/browse/AMBARI-16028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15254719#comment-15254719 ] Hudson commented on AMBARI-16028: - FAILURE: Integrated in Ambari-branch-2.2 #663 (See

[jira] [Commented] (AMBARI-16028) Namenode marked as INITIAL standby could potentially never start if other namenode is down

[ https://issues.apache.org/jira/browse/AMBARI-16028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15254660#comment-15254660 ] Hudson commented on AMBARI-16028: - SUCCESS: Integrated in Ambari-trunk-Commit #4717 (See

[jira] [Commented] (AMBARI-16028) Namenode marked as INITIAL standby could potentially never start if other namenode is down

[ https://issues.apache.org/jira/browse/AMBARI-16028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15254446#comment-15254446 ] Jayush Luniya commented on AMBARI-16028: Committed to trunk and branch-2.2 (so that the change

[jira] [Commented] (AMBARI-16028) Namenode marked as INITIAL standby could potentially never start if other namenode is down

[ https://issues.apache.org/jira/browse/AMBARI-16028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15253499#comment-15253499 ] Hadoop QA commented on AMBARI-16028: {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (AMBARI-16028) Namenode marked as INITIAL standby could potentially never start if other namenode is down

[ https://issues.apache.org/jira/browse/AMBARI-16028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15252864#comment-15252864 ] Jayush Luniya commented on AMBARI-16028: *Fix:* # The fix is to maintain a bootstrap marker file