You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Siddharth Wagle (JIRA)" <ji...@apache.org> on 2014/03/26 01:16:19 UTC
[jira] [Resolved] (AMBARI-5216) stale_configs parameter works not
properly after removing config group
[ https://issues.apache.org/jira/browse/AMBARI-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siddharth Wagle resolved AMBARI-5216.
-------------------------------------
Resolution: Fixed
Committed to 1.5.0 and trunk.
> stale_configs parameter works not properly after removing config group
> ----------------------------------------------------------------------
>
> Key: AMBARI-5216
> URL: https://issues.apache.org/jira/browse/AMBARI-5216
> Project: Ambari
> Issue Type: Bug
> Components: controller
> Affects Versions: 1.5.0
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Fix For: 1.5.0
>
>
> *Steps:*
> # Deployed 3-node cluster.
> # Added new config group for HDFS service.
> # Assigned to newly created group 2 hosts.
> # Overrided property *DataNode maximum Java heap size* from value 1024 to 1025.
> # Executed rolling restart of DataNodes so for them maxJavaHeapSize became to 1025.
> # Removed newly created group and assigned to HDFS default (where maxJavaHeapSize is 1024).
> *Result*: Restart indicator is absent for HDFS service after deleting config group with custom property.
--
This message was sent by Atlassian JIRA
(v6.2#6252)