You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2019/06/28 13:25:00 UTC
[jira] [Created] (OAK-8448) VersionGC may get stuck at 60s scope
Julian Reschke created OAK-8448:
-----------------------------------
Summary: VersionGC may get stuck at 60s scope
Key: OAK-8448
URL: https://issues.apache.org/jira/browse/OAK-8448
Project: Jackrabbit Oak
Issue Type: Bug
Components: documentmk
Affects Versions: 1.8.9
Reporter: Julian Reschke
Assignee: Julian Reschke
It seems that if the VersionGarbageCollector reduces the scope to a 60s interval, it'll never change it back to a bigger interval. This is because the collectLimit gets set to 0:
{noformat}
if (scope.getDurationMs() <= options.precisionMs) {
// If we have narrowed the collect time interval down as much as we can, no
// longer enforce a limit. We need to get through this.
collectLimit = 0;
log.debug("time interval <= precision ({} ms), disabling collection limits", options.precisionMs);
}
{noformat}
...and later on this is interpreted as "there were no restrictions in the prior run that need to be updated":
{noformat}
if (maxCollect <= 0) {
log.debug("successful run without effective limit, keeping recommendations");
}
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)