[
https://issues.apache.org/jira/browse/AMBARI-16024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252616#comment-15252616
]
jun aoki commented on AMBARI-16024:
-----------------------------------
[~bhuvnesh2703], I might be missing some background context but have a question.
In general, changing topology (in this case removing standby) and followed by
performing a service check is a right thing to do.
The problem occurs when HDFS HA, but is Remove Standby wizard OK when HDFS
non-HA?
I'd rather keep Service Check running on Remove Standby wizard, but fix a
wizard to enable HDFS HA to update "the old filespace"? Just my 2 cents
> Remove performing service check during "Remove Standby Wizard"
> --------------------------------------------------------------
>
> Key: AMBARI-16024
> URL: https://issues.apache.org/jira/browse/AMBARI-16024
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.2.0
> Reporter: bhuvnesh chaudhary
> Assignee: bhuvnesh chaudhary
> Fix For: 2.3.0
>
> Attachments: AMBARI-16024.patch
>
>
> Users will need to remove the HAWQ Standby Master using "Remove Standby
> Wizard" after enabling HDFS HA.
> So the service check may fail during the wizard as the HAWQ catalog might be
> still pointing to the old filespace.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
