[
https://issues.apache.org/jira/browse/ACCUMULO-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15446234#comment-15446234
]
Josh Elser commented on ACCUMULO-4428:
--------------------------------------
He means each cycle the GC runs (it's "period")
{code}
Span waLogs = Trace.start("walogs");
try {
GarbageCollectWriteAheadLogs walogCollector = new
GarbageCollectWriteAheadLogs(this, fs, isUsingTrash());
log.info("Beginning garbage collection of write-ahead logs");
walogCollector.collect(status);
} catch (Exception e) {
log.error("{}", e.getMessage(), e);
} finally {
waLogs.stop();
}
gcSpan.stop();
{code}
> GC does not delete WAL files belonging to dead tservers
> -------------------------------------------------------
>
> Key: ACCUMULO-4428
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4428
> Project: Accumulo
> Issue Type: Bug
> Affects Versions: 1.7.2
> Reporter: Adam J Shook
> Priority: Blocker
> Fix For: 1.7.3, 1.8.1
>
>
> The GarbageCollectWriteAheadLogs uses a Map<HostAndPort,Long> to track when
> it had first seen a dead tserver, waiting an hour before deleting the files.
> However, a new instance of this class is re-created during each run of the
> SimpleGarbageCollector, causing the state of the dead tservers to be lost.
> All of the WAL files belonging to a dead tserver will never be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
