[jira] [Created] (AMBARI-5884) Slave components in decommission state restart during corresponding Service restarts, but they should not

["Srimanth Gunturi (JIRA)" <ji...@apache.org>]

Srimanth Gunturi created AMBARI-5884:
----------------------------------------

             Summary: Slave components in decommission state restart during corresponding Service restarts, but they should not
                 Key: AMBARI-5884
                 URL: https://issues.apache.org/jira/browse/AMBARI-5884
             Project: Ambari
          Issue Type: Bug
          Components: controller
    Affects Versions: 1.6.0
         Environment: Centos6.4/5.9, SUSE11,
stack 2.1
ambari server version: 1.6.0.20
hash: 186db4e0cdc6ec9d4f4ca6176895acda36ef203b
            Reporter: Srimanth Gunturi
             Fix For: 1.6.1


Slave components in decommission state restart with other service components during Service Restart operation, but it should not.

*STR:*
1) Deploy cluster by default
2) Turn any slave component to Decommission state (e.g. Datanode)
3) Go to Services page and Restart corresponding service (HDFS)

*Expected result:* Datanode in Decommission state should not restart with other HDFS components

*Actual result:* Datanode in Decommission state restarts with other HDFS components



--
This message was sent by Atlassian JIRA
(v6.2#6252)