accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1773) Garbage collector may delete referenced files after upgrade
Date Fri, 11 Oct 2013 16:22:42 GMT

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

Keith Turner commented on ACCUMULO-1773:
----------------------------------------

Discussed this with [~ecn] and [~ctubbsii] and we decided to only use the suffix /<accumulo
dir>/tables/<table id>/<tablet dir>/<file> for determining if a file
is referenced.   Since file names are unique this should not lead to false negatives (decide
not to delete something that should be deleted).  But even if it did, a bug w/ false negatives
would be preferable to false positives.   

> Garbage collector may delete referenced files after upgrade
> -----------------------------------------------------------
>
>                 Key: ACCUMULO-1773
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1773
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: master, tserver
>            Reporter: Keith Turner
>            Priority: Blocker
>             Fix For: 1.6.0
>
>
> Looking at the srouce code, it seems like the garbage collector uses a mixture of relative
and absolute paths when determining what files to delete.  I think if a deletion candidate
is an absolute path and the reference is a relative path then it could delete the referenced
file.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message