[
https://issues.apache.org/jira/browse/ACCUMULO-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13852177#comment-13852177
]
Keith Turner commented on ACCUMULO-1771:
----------------------------------------
bq. Does using HDFS Federation just make this problem go away?
If you have two federated namenodes and configure Accumulo to use both with a
config like the following, then only hdfs://nn1/accumulo will be initialized
with an instance id. If you change the following config, Accumulo may break.
{noformat}
<property>
<name>instance.volumes</name>
<value>hdfs://nn1,hdfs://nn2</value>
</property>
{noformat}
> Instance id and version info only stored on one hdfs instance
> -------------------------------------------------------------
>
> Key: ACCUMULO-1771
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1771
> Project: Accumulo
> Issue Type: Sub-task
> Components: master, tserver
> Reporter: Keith Turner
> Priority: Critical
> Fix For: 1.6.0
>
>
> When instance.volumes contains multiple uris only the first one is
> initialized with the data version and instance id. If the user changes the
> order of the uris in the config, it seems like Accumulo will stop working
> correctly.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
