[
https://issues.apache.org/jira/browse/OAK-5119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vikas Saurabh updated OAK-5119:
-------------------------------
Summary: JournalGarbageCollector: journalGcBatchSize configuration is
irrelevant post implementation tasks of bulk remove support in DocumentStore
(was: JourncalGarbageCollector: journalGcBatchSize configuration is irrelevant
post implementation tasks of bulk remove support in DocumentStore)
> 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.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)
