Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Wed, 1 Jun 2011 21:44:49 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <1134527432.61073.1306964689131.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HADOOP-7001) Allow configuration changes
 without restarting configured nodes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on HADOOP-7001:
--------------------------------

Integrated in Hadoop-Common-22-branch #60 (See [https://builds.apache.org/hudson/job/Hadoop-Common-22-branch/60/])
    Merging changes r1038493 and r1038480 for HADOOP-7001 from trunk

suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1130306
Files : 
* /hadoop/common/branches/branch-0.22/src/docs
* /hadoop/common/branches/branch-0.22/src/java/org/apache/hadoop/conf/ReconfigurableBase.java
* /hadoop/common/branches/branch-0.22
* /hadoop/common/branches/branch-0.22/src/java/org/apache/hadoop/conf/Reconfigurable.java
* /hadoop/common/branches/branch-0.22/src/java/org/apache/hadoop/conf/ReconfigurationException.java
* /hadoop/common/branches/branch-0.22/src/test/core
* /hadoop/common/branches/branch-0.22/src/test/core/org/apache/hadoop/io/TestSequenceFile.java
* /hadoop/common/branches/branch-0.22/CHANGES.txt
* /hadoop/common/branches/branch-0.22/src/java
* /hadoop/common/branches/branch-0.22/src/java/org/apache/hadoop/conf/Configuration.java
* /hadoop/common/branches/branch-0.22/src/test/core/org/apache/hadoop/conf/TestReconfiguration.java
* /hadoop/common/branches/branch-0.22/src/java/org/apache/hadoop/conf/ReconfigurationUtil.java
* /hadoop/common/branches/branch-0.22/src/java/org/apache/hadoop/conf/ReconfigurationServlet.java


> Allow configuration changes without restarting configured nodes
> ---------------------------------------------------------------
>
>                 Key: HADOOP-7001
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7001
>             Project: Hadoop Common
>          Issue Type: Task
>          Components: conf
>    Affects Versions: 0.23.0
>            Reporter: Patrick Kling
>            Assignee: Patrick Kling
>             Fix For: 0.23.0
>
>         Attachments: HADOOP-7001.2.patch, HADOOP-7001.3.patch, HADOOP-7001.4.patch, HADOOP-7001.5.patch, HADOOP-7001.patch, reconfigurable.patch
>
>
> Currently, changing the configuration on a node (e.g., the name node) requires that we restart the node. We propose a change that would allow us to make configuration changes without restarting. Nodes that support configuration changes at run time should implement the following interface:
> interface ChangeableConfigured extends Configured {
>    void changeConfiguration(Configuration newConf) throws ConfigurationChangeException;
> }
> The contract of changeConfiguration is as follows:
> The node will compare newConf to the existing configuration. For each configuration property that is set to a different value than in the current configuration, the node will either adjust its behaviour to conform to the new configuration or throw a ConfigurationChangeException if this change is not possible at run time. If a configuration property is set in the current configuration but is unset in newConf, the node should use its default value for this property. After a successful invocation of changeConfiguration, the behaviour of the configured node should be indistinguishable from the behaviour of a node that was configured with newConf at creation.
> It should be easy to change existing nodes to implement this interface. We can start by throwing the exception for all changes and then gradually start supporting more and more changes at run time. (We might even consider replacing Configured with ChangeableConfigured entirely, but I think the proposal above afford greater flexibility).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira