Description
Consider using full path names to files, which would allow the servers to access the files on any HDFS file system.
Work may exist elsewhere to run HDFS using a number of NameNode instances to break up the namespace.
We may need a pluggable strategy to determine namespace for new files.
Attachments
Attachments
Issue Links
- is related to
-
ACCUMULO-2274 AddFilesWithMissingEntries needs to support multiple volumes
- Resolved
-
ACCUMULO-2974 Unable to assign single tablet table migrated to 1.6.0
- Resolved
-
ACCUMULO-1902 DefaultSecretKeyEncryptionStrategy will not work w/ multiple namenodes
- Resolved
-
ACCUMULO-2530 Update crypto properties and encryption strategies to be volume-aware
- Resolved
-
ACCUMULO-1524 Abstract file pointers in metadata table
- Open
-
ACCUMULO-2552 Check for usage of FileSystem.get(Configuration)
- Resolved
-
ACCUMULO-3535 Transition plan: remove instance.dfs.{uri,dir} to instance.volumes
- Resolved
- relates to
-
ACCUMULO-1747 ServerConstants.getBaseDirs() use fs default name, not instance.dfs.uri
- Resolved
-
ACCUMULO-1685 bench testing shows that the NN loses the WAL
- Resolved
-
ACCUMULO-722 Accumulo using Accumulo as its own NameNode
- Resolved