Description
In addition to heterogeneous media, many applications work with heterogeneous storage systems. The guarantees and semantics provided by these systems are often similar, but not identical to those of HDFS. Any client accessing multiple storage systems is responsible for reasoning about each system independently, and must propagate/and renew credentials for each store.
Remote stores could be mounted under HDFS. Block locations could be mapped to immutable file regions, opaque IDs, or other tokens that represent a consistent view of the data. While correctness for arbitrary operations requires careful coordination between stores, in practice we can provide workable semantics with weaker guarantees.
Attachments
Attachments
Issue Links
- incorporates
-
HDFS-10706 [READ] Add tool generating FSImage from external store
- Resolved
- is depended upon by
-
HDFS-13069 Enable HDFS to cache data read from external storage systems
- Open
- is related to
-
HDFS-11125 [SPS]: Use smaller batches of BlockMovingInfo into the block storage movement command
- Resolved
-
HDFS-15660 StorageTypeProto is not compatiable between 3.x and 2.6
- Resolved
-
HDFS-14805 Mounting external stores in HDFS on-the-fly
- Open
-
HDFS-7878 API - expose a unique file identifier
- Resolved
-
HDFS-9807 Add an optional StorageID to writes
- Resolved
-
HDFS-9808 Combine READ_ONLY_SHARED DatanodeStorages with the same ID
- Resolved
-
HDFS-12882 Support full open(PathHandle) contract in HDFS
- Resolved
- relates to
-
HDFS-12090 Handling writes from HDFS to Provided storages
- Open
-
HDFS-13536 [PROVIDED Storage] HA for InMemoryAliasMap
- Resolved
-
HDFS-14390 Provide kerberos support for AliasMap service used by Provided storage
- Resolved
-
HDFS-9810 Allow support for more than one block replica per datanode
- Open
-
HDFS-9809 Abstract implementation-specific details from the datanode
- Resolved