[
https://issues.apache.org/jira/browse/ACCUMULO-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14070473#comment-14070473
]
Christopher Tubbs commented on ACCUMULO-3006:
---------------------------------------------
I'm not sure I agree that viewfs should be disallowed simply because it has
certain preconditions to function properly. Rather, it should be made clear in
our documentation that the user is responsible for establishing any necessary
preconditions (like core-site.xml on the classpath), and we can highlight the
known issues (such as the problem when the trash is enabled and there is no
mapping). We can also take care to remove any recommendation to use viewfs, due
to the complexity of configuration.
So, I'd prefer this issue be changed to a documentation improvement to update
the multivolume chapter in the manual, given its limitations, rather than to
disable the feature entirely.
Now, if there are any outstanding issues with the functionality of Accumulo and
ViewFS that does not represent satisfying a precondition in configuration, then
separate issues should be filed to fix those in a separate JIRA for resolution
(if possible).
> Don't allow viewfs in instance.volumes
> --------------------------------------
>
> Key: ACCUMULO-3006
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3006
> Project: Accumulo
> Issue Type: Bug
> Affects Versions: 1.6.0
> Reporter: Dave Marion
> Priority: Blocker
> Fix For: 1.6.1, 1.7.0
>
>
> I think one of our folks put viewfs into instance.volumes on accident. File
> references in accumulo.root and accumulo.metadata were then written with
> viewfs in the path. The garbage collector then throws errors as compactions
> occur and it tries delete and move the files to the hdfs users trash
> directory.
> viewfs should never be allowed in instance.volumes property. It should fail.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
