[
https://issues.apache.org/jira/browse/ACCUMULO-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13245562#comment-13245562
]
Dave Marion commented on ACCUMULO-118:
--------------------------------------
Just thinking...
Configure Accumulo with one default namespace (ns1) for the system. Tables
created with no namespace specified will go into ns1. Tables created with
namespaces defined (ns2, ns3, etc) will use some default file creation load
balancer (round-robin). Allow tables to use user-defined file creation load
balancers. This might lead to defining back-up namespaces (ns4, ns5) later
(Just a thought).
Will need to provide a utility for moving files between namespaces so that the
!METADATA table is updated correctly.
> accumulo could work across HDFS instances, which would help it to scale past
> a single namenode
> ----------------------------------------------------------------------------------------------
>
> Key: ACCUMULO-118
> URL: https://issues.apache.org/jira/browse/ACCUMULO-118
> Project: Accumulo
> Issue Type: Improvement
> Components: master, tserver
> Affects Versions: 1.5.0
> Reporter: Eric Newton
> Assignee: Eric Newton
> Original Estimate: 2,016h
> Remaining Estimate: 2,016h
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
