[jira] [Commented] (AMBARI-23493) Decommission Datanode doesn't work

2018-04-12 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/AMBARI-23493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16436275#comment-16436275
 ] 

Hudson commented on AMBARI-23493:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9044 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/9044/])
Revert "[AMBARI-23493] Decommission Datanode doesn't work (dsen)" (avijayan: 
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=5ab9037ff820d312a747547226225d6b5911])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelper.java
* (edit) 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/utils/StageUtils.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/utils/StageUtilsTest.java
* (edit) 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py


> Decommission Datanode doesn't work
> --
>
> Key: AMBARI-23493
> URL: https://issues.apache.org/jira/browse/AMBARI-23493
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> On an Ambari270 cluster, try to decommission a datanode.
> You could see bgop is triggerred and shows as sucsessful.
> But Datanode seems to be still in started state and Decommission op is still 
> available in dropdown.
> The issue is caused by recent perf changes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (AMBARI-23493) Decommission Datanode doesn't work

2018-04-12 Thread Aravindan Vijayan (JIRA)

[ 
https://issues.apache.org/jira/browse/AMBARI-23493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16436208#comment-16436208
 ] 

Aravindan Vijayan commented on AMBARI-23493:


This commit was reverted due to revert of dependent commit from AMBARI-23370.

> Decommission Datanode doesn't work
> --
>
> Key: AMBARI-23493
> URL: https://issues.apache.org/jira/browse/AMBARI-23493
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> On an Ambari270 cluster, try to decommission a datanode.
> You could see bgop is triggerred and shows as sucsessful.
> But Datanode seems to be still in started state and Decommission op is still 
> available in dropdown.
> The issue is caused by recent perf changes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (AMBARI-23493) Decommission Datanode doesn't work

2018-04-12 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/AMBARI-23493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16435394#comment-16435394
 ] 

Hudson commented on AMBARI-23493:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9037 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/9037/])
[AMBARI-23493] Decommission Datanode doesn't work (dsen) (dsen: 
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=675ca9a64f70fae517aeefcadcbab137a239922a])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/utils/StageUtils.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerTest.java
* (edit) 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelper.java
* (edit) 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/utils/StageUtilsTest.java


> Decommission Datanode doesn't work
> --
>
> Key: AMBARI-23493
> URL: https://issues.apache.org/jira/browse/AMBARI-23493
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
>  Labels: pull-request-available
> Fix For: 2.7.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> On an Ambari270 cluster, try to decommission a datanode.
> You could see bgop is triggerred and shows as sucsessful.
> But Datanode seems to be still in started state and Decommission op is still 
> available in dropdown.
> The issue is caused by recent perf changes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)