[
https://issues.apache.org/jira/browse/HDFS-15120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17053140#comment-17053140
]
Jinglun commented on HDFS-15120:
--------------------------------
Hi [~ayushtkn], sorry for my late response. The new key-value can be loaded
because in NameNode.reconfBlockPlacementPolicy() we call method getNewConf().
That will reload the key-value from the core-site.xml and hdfs-site.xml on disk.
The unit test is not clear, shouldn't use the default value. I'll fix it.
> 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
> Fix For: 3.3.0
>
> Attachments: HDFS-15120.001.patch, HDFS-15120.002.patch,
> HDFS-15120.003.patch, HDFS-15120.004.patch, HDFS-15120.005.patch,
> HDFS-15120.006.patch, HDFS-15120.007.1.patch, HDFS-15120.007.patch,
> HDFS-15120.008.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]
