[
https://issues.apache.org/jira/browse/ACCUMULO-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13807683#comment-13807683
]
ASF subversion and git services commented on ACCUMULO-1773:
-----------------------------------------------------------
Commit 72fdef3d589b9122b562bf8c89a4f22535f460d0 in branch refs/heads/master
from [~elserj]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=72fdef3 ]
ACCUMULO-1773 Review and minor changes to GarbageCollection rework.
Add shortcircuit when scanning candidates for any files which might be in a
bulk load. Add javadoc to the GarbageCollectionEnvironment to actually describe
what the interface should be doing. Remove old 'offline' warning message
as the option itself is gone. Added TODO about caught exception when
trying to write deletes. Removed unnecessary string concat in
ChooseDir.
> 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
> Assignee: 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)
