[
https://issues.apache.org/jira/browse/ACCUMULO-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13871527#comment-13871527
]
Christopher Tubbs commented on ACCUMULO-1771:
---------------------------------------------
[~vines]: Previous versions could only run on a single DFS, so it's a
non-issue. Upgrades can still read the hdfs path if there is a single
filesystem and the property is not set. Otherwise, the instance name would need
to be added when volumes are added to the config. So, there's no additional
distribution necessary... and certainly no init necessary (for upgrades). We
could add an error if the instance name is not set, in the case of multiple
volumes and document that it should generally be set (warn if not, when using a
single volume, such as in the case of trying to re-use an old config example
for a brand new instance).
> 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
> Assignee: 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.5#6160)
