You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "John Vines (JIRA)" <ji...@apache.org> on 2013/10/26 02:40:30 UTC
[jira] [Issue Comment Deleted] (ACCUMULO-1766) Changing Accumulo
config can prevent locating root table files.
[ https://issues.apache.org/jira/browse/ACCUMULO-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Vines updated ACCUMULO-1766:
---------------------------------
Comment: was deleted
(was: Is this a dupe or abstraction of ACCUMULO-1766?)
> Changing Accumulo config can prevent locating root table files.
> ---------------------------------------------------------------
>
> Key: ACCUMULO-1766
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1766
> Project: Accumulo
> Issue Type: Sub-task
> Components: master, tserver
> Reporter: Keith Turner
> Priority: Blocker
> Fix For: 1.6.0
>
>
> Looking at the code related to the root tablet I think it currently chooses the first uri listed in instance.volumes and uses that to store root table files. If this config changes it seems like Accumulo will not see its root table files.
> Two possible ways of handling this are
>
> # Have init choose a uri from instance.volumes and store that in zookeeper, much like each tablet uri is chosen and stored in the metadata table.
> # user all namenodes listed in instance.volumes to store root table files.
> #1 seems like the best option. #2 is still vulnerable to config changes causing a problem
--
This message was sent by Atlassian JIRA
(v6.1#6144)