-
Type:
Improvement
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.9.0, 3.0.0-alpha1, 2.8.2
-
Component/s: None
-
Labels:None
Current HDFS DN rolling upgrade step requires sequential DN restart to minimize the impact on data availability and read/write operations. The side effect is longer upgrade duration for large clusters. This might be acceptable for DN JVM quick restart to update hadoop code/configuration. However, for OS upgrade that requires machine reboot, the overall upgrade duration will be too long if we continue to do sequential DN rolling restart.
- is related to
-
HDFS-14637 Namenode may not replicate blocks to meet the policy after enabling upgradeDomain
-
- Resolved
-
-
AMBARI-24301 API for HDFS Upgrade Domains management for scripted node additions
-
- Open
-
-
HDFS-8789 Block Placement policy migrator
-
- Open
-
-
HDFS-7877 [Umbrella] Support maintenance state for datanodes
-
- Resolved
-
-
HDFS-13742 HDFS Upgrade Domains dynamic placement policy using dfsadmin commands and scripting API to be automation friendly for scripted datanode additions to clusters
-
- Open
-
- relates to
-
YARN-8256 Pluggable provider for node membership management
-
- Open
-
-
HDFS-1431 Balancer should work with the logic of BlockPlacementPolicy
-
- Open
-
-
HDFS-3566 Custom Replication Policy for Azure
-
- Resolved
-
-
HDFS-13739 Add option to disable rack local write preference
-
- Resolved
-