You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Ming Ma (JIRA)" <ji...@apache.org> on 2014/10/10 21:53:34 UTC
[jira] [Commented] (HADOOP-10376) Refactor refresh*Protocols into a
single generic refreshConfigProtocol
[ https://issues.apache.org/jira/browse/HADOOP-10376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167400#comment-14167400 ]
Ming Ma commented on HADOOP-10376:
----------------------------------
Interesting work. There is org.apache.hadoop.conf.Reconfigurable defined to support config update at run time. Should we deprecate that interface and provide reconfiguration based on RefreshHandler?
> Refactor refresh*Protocols into a single generic refreshConfigProtocol
> ----------------------------------------------------------------------
>
> Key: HADOOP-10376
> URL: https://issues.apache.org/jira/browse/HADOOP-10376
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Chris Li
> Assignee: Chris Li
> Priority: Minor
> Fix For: 2.5.0
>
> Attachments: HADOOP-10376.patch, HADOOP-10376.patch, HADOOP-10376.patch, HADOOP-10376.patch, HADOOP-10376.patch, RefreshFrameworkProposal.pdf
>
>
> See https://issues.apache.org/jira/browse/HADOOP-10285
> There are starting to be too many refresh*Protocols We can refactor them to use a single protocol with a variable payload to choose what to do.
> Thereafter, we can return an indication of success or failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)