[
https://issues.apache.org/jira/browse/HDFS-15120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17041688#comment-17041688
]
Ayush Saxena commented on HDFS-15120:
-------------------------------------
I am not catching what is the problem with just adding, it as a reconfigurable
property, like others.
Can add the conf here in {{Namenode.java}}
{code:java}
/** A list of property that are reconfigurable at runtime. */
private final TreeSet<String> reconfigurableProperties = Sets
.newTreeSet(Lists.newArrayList(
DFS_HEARTBEAT_INTERVAL_KEY,
DFS_NAMENODE_HEARTBEAT_RECHECK_INTERVAL_KEY,
FS_PROTECTED_DIRECTORIES,
HADOOP_CALLER_CONTEXT_ENABLED_KEY));
{code}
and handle it as part of {{reconfigurePropertyImpl(String property, String
newVal)}}, that is how all other configurations which are supposed to be
updated at runtime are handled.
IMO going with existing way is better rather than having a new command
> Refresh BlockPlacementPolicy at runtime.
> ----------------------------------------
>
> Key: HDFS-15120
> URL: https://issues.apache.org/jira/browse/HDFS-15120
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Jinglun
> Assignee: Jinglun
> Priority: Major
> Attachments: HDFS-15120.001.patch, HDFS-15120.002.patch,
> HDFS-15120.003.patch, HDFS-15120.004.patch, HDFS-15120.005.patch
>
>
> Now if we want to switch BlockPlacementPolicies we need to restart the
> NameNode. It would be convenient if we can switch it at runtime. For example
> we can switch between AvailableSpaceBlockPlacementPolicy and
> BlockPlacementPolicyDefault as needed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
