-
Notifications
You must be signed in to change notification settings - Fork 9.2k
HDFS-17868. introduce BlockPlacementPolicyCrossDC for multi datacenter stretched hdfs cluster #8159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: trunk
Are you sure you want to change the base?
Conversation
…r stretched hdfs cluster
| || property.equals(DFS_BLOCK_REPLICATOR_CROSS_DC_BANDWIDTH_LIMIT_MB_KEY) | ||
| || property.equals(DFS_BLOCK_REPLICATOR_CROSS_DC_BANDWIDTH_REFILL_PERIOD_SEC_KEY) | ||
| || property.equals(DFS_BLOCK_REPLICATOR_CROSS_DC_SYNC_PATHS_KEY) | ||
| || property.equals(DFS_BLOCK_REPLICATOR_CROSS_DC_LIMITED_SYNC_PATHS_KEY) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In order to change configurations without restarting NameNode, I added BlockPlacementStatusWithCrossDC related configurations here.
However, if you change multiple configurations simultaneously and reconfigure it, reconfBlockPlacementPolicy() called multiple times.
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
Description of PR
I wrote description on https://issues.apache.org/jira/browse/HDFS-17868.
How was this patch tested?
Manual test on the private hdfs cluster.
For code changes:
LICENSE,LICENSE-binary,NOTICE-binaryfiles?