accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1766) Changing Accumulo config can prevent locating root table files.
Date Sat, 26 Oct 2013 04:02:30 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13805989#comment-13805989
] 

John Vines commented on ACCUMULO-1766:
--------------------------------------

Requiring users to run updates in the past has done nothing but cause headaches for both users
and developers. The more hands off the migration, the better, because then it's harder for
it to get screwed up.

> 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)

Mime
View raw message