[jira] [Commented] (AMBARI-16024) Remove performing service check during "Remove Standby Wizard"
[ https://issues.apache.org/jira/browse/AMBARI-16024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15258979#comment-15258979 ] Hudson commented on AMBARI-16024: - SUCCESS: Integrated in Ambari-branch-2.2 #672 (See [https://builds.apache.org/job/Ambari-branch-2.2/672/]) AMBARI-16024: Remove performing service check during Remove Standby (bchaudhary: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a358ea1232c9d8d543c07fb88b697a00d4780d45]) * ambari-web/app/controllers/main/admin/highAvailability/hawq/removeStandby/step3_controller.js > 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-1.patch, 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)
[jira] [Commented] (AMBARI-16024) Remove performing service check during "Remove Standby Wizard"
[ https://issues.apache.org/jira/browse/AMBARI-16024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15258897#comment-15258897 ] Hudson commented on AMBARI-16024: - SUCCESS: Integrated in Ambari-trunk-Commit #4742 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4742/]) AMBARI-16024: Remove performing service check during Remove Standby (bchaudhary: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=39320fd8ada68ee4bfbb016926f1f3c69508cca7]) * ambari-web/app/controllers/main/admin/highAvailability/hawq/removeStandby/step3_controller.js > 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-1.patch, 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)
[jira] [Commented] (AMBARI-16024) Remove performing service check during "Remove Standby Wizard"
[
https://issues.apache.org/jira/browse/AMBARI-16024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15257634#comment-15257634
]
Hadoop QA commented on AMBARI-16024:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12800643/AMBARI-16024-1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6651//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6651//console
This message is automatically generated.
> 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-1.patch, 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)
[jira] [Commented] (AMBARI-16024) Remove performing service check during "Remove Standby Wizard"
[ https://issues.apache.org/jira/browse/AMBARI-16024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15252680#comment-15252680 ] bhuvnesh chaudhary commented on AMBARI-16024: - In case of Non-HA we might not see the problem listed in the jira but my above comment describes the other problem which we see because of segments not being registered early enough. What you mentioned, in general service check is a good thing, i agree with that. > 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)
[jira] [Commented] (AMBARI-16024) Remove performing service check during "Remove Standby Wizard"
[ https://issues.apache.org/jira/browse/AMBARI-16024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15252647#comment-15252647 ] bhuvnesh chaudhary commented on AMBARI-16024: - Also, we do execute the service check as part of the api calling start, so often it happens that the segments have not registered and due to which service check fails, so we should not do it here in my opinion. We can definitely add the service check but we should find out a way to identify the right time to run the service check. > 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)
[jira] [Commented] (AMBARI-16024) Remove performing service check during "Remove Standby Wizard"
[ https://issues.apache.org/jira/browse/AMBARI-16024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
