accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Marion (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3006) Don't allow viewfs in instance.volumes
Date Tue, 22 Jul 2014 17:20:39 GMT

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

Dave Marion commented on ACCUMULO-3006:
---------------------------------------

In this case it is not entirely transparent to the application, see: 

SimpleGarbageCollector.moveToTrash() and VolumeManagerImpl.moveToTrash(). 

The trash policy is set for the underlying HDFS instances, but there is no mapping in the
viewfs definition for /user. If there was a viewfs definition for /user, it would fail anyway
in the case where you are trying to put a file from one nameservice into the trash directory
that is mounted from a different nameservice (this would equate to a file move across nameservices).




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

Mime
View raw message