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 "Vikas Saurabh (JIRA)" <ji...@apache.org> on 2016/11/16 15:43:59 UTC
[jira] [Resolved] (OAK-5119) JournalGarbageCollector:
journalGcBatchSize configuration is irrelevant post implementation tasks of
bulk remove support in DocumentStore
[ https://issues.apache.org/jira/browse/OAK-5119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vikas Saurabh resolved OAK-5119.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.6
Done on trunk at [r1770004|https://svn.apache.org/r1770004].
> JournalGarbageCollector: journalGcBatchSize configuration is irrelevant post implementation tasks of bulk remove support in DocumentStore
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: OAK-5119
> URL: https://issues.apache.org/jira/browse/OAK-5119
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: documentmk
> Reporter: Vikas Saurabh
> Assignee: Vikas Saurabh
> Priority: Minor
> Fix For: 1.6, 1.5.14
>
>
> Following up with this [comment|https://issues.apache.org/jira/browse/OAK-3001?focusedCommentId=15670100&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15670100]:
> {quote}
> ... noticed OAK-3975 in related issues. I think we should revert that configuration and code for house-keeping/maintenance!?
> {quote}
> OAK-3875 added a configuration to {{DocumentNodeStoreService}} to have configurable batch sizes while removing journal entries. With implementation tasks of OAK-3001, we do bulk remove at persistence layer and hence batched query isn't required. Thus, the configuration should be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)