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 "Stefan Egli (Jira)" <ji...@apache.org> on 2024/07/03 16:17:00 UTC
[jira] [Commented] (OAK-10933) Avoid log about calculating fullGCTimestamp when fullGC is disabled
[ https://issues.apache.org/jira/browse/OAK-10933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862841#comment-17862841 ]
Stefan Egli commented on OAK-10933:
-----------------------------------
PR created : https://github.com/apache/jackrabbit-oak/pull/1570
> Avoid log about calculating fullGCTimestamp when fullGC is disabled
> -------------------------------------------------------------------
>
> Key: OAK-10933
> URL: https://issues.apache.org/jira/browse/OAK-10933
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: documentmk
> Reporter: Stefan Egli
> Assignee: Stefan Egli
> Priority: Minor
>
> With fullgc disabled below info message were seen - they should be avoided :
> {noformat}
> 01.02.2013 10:11:12.014 *INFO* [sling-oak-1-org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreService$RevisionGCJob] org.apache.jackrabbit.oak.plugins.document.VersionGCRecommendations No fullGCTimestamp found, querying for the oldest modified candidate
> 01.02.2013 10:11:12.015 *INFO* [sling-oak-1-org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreService$RevisionGCJob] org.apache.jackrabbit.oak.plugins.document.VersionGCRecommendations fullGCTimestamp found: 2004-01-02 23:24:25.026
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)