[
https://issues.apache.org/jira/browse/ACCUMULO-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13852315#comment-13852315
]
Mike Drob commented on ACCUMULO-1771:
-------------------------------------
What's the use case for running Accumulo with different kinds of volumes? That
seems like it would be rife with consistency problems, and I would have a tough
time recommending to users that they should stripe their data across HDFS and
NFS, for example. Or even HDFS and MapR - the added complexity in that space is
huge (as we're seeing from this and related issues). This JIRA may not be the
place to have this conversation, but I'd definitely want to see us moving
closer to what the rest of the Hadoop community is doing so that we can benefit
from the 'free work' that it may provide.
> 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)
