[
https://issues.apache.org/jira/browse/OAK-4863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger resolved OAK-4863.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.5.11
The batch now contains up to 1000 documents and can be tweaked with a system
property {{oak.mongo.queryDeletedDocsBatchSize}}.
Fixed in trunk: http://svn.apache.org/r1762825
> Reduce query batch size for deleted documents
> ---------------------------------------------
>
> Key: OAK-4863
> URL: https://issues.apache.org/jira/browse/OAK-4863
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: mongomk
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Minor
> Labels: resilience
> Fix For: 1.6, 1.5.11
>
>
> MongoVersionGCSupport uses the default batchSize when it queries for possibly
> deleted documents. The default will initially read 100 documents and then as
> many as fit into a 4MB response. Depending on the document size a couple of
> thousand will fit in there and take time to process. It may happen that the
> MongoDB cursor then times out and the VersionGC fails.
> An easy and safe solution is to reduce the batch size to a given number of
> documents.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
