Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.0.0-alpha2
-
None
-
None
-
Reviewed
Description
The BlockPlacementPolicy considers specific storages, but when the replica is written the DN VolumeChoosingPolicy is unaware of any preference or constraints from other policies affecting placement. This limits heterogeneity to the declared storage types, which are treated as fungible within the target DN. It should be possible to influence or constrain the DN policy to select a particular storage.
Attachments
Attachments
Issue Links
- breaks
-
HDFS-12151 Hadoop 2 clients cannot writeBlock to Hadoop 3 DataNodes
- Resolved
-
HDFS-11956 Do not require a storage ID or target storage IDs when writing a block
- Resolved
- causes
-
HDFS-13941 make storageId in BlockPoolTokenSecretManager.checkAccess optional
- Resolved
- is related to
-
HDFS-11464 Improve the selection in choosing storage for blocks
- Patch Available
-
HDFS-12207 A few DataXceiver#writeBlock cleanups related to optional storage IDs and types
- Open
-
HDFS-14330 Consider StorageID to choose volume
- Open
- relates to
-
HDFS-6708 StorageType should be encoded in the block token
- Resolved
-
HDFS-9806 Allow HDFS block replicas to be provided by an external storage system
- Resolved
-
HDFS-11419 BlockPlacementPolicyDefault is choosing datanode in an inefficient way
- Resolved