[
https://issues.apache.org/jira/browse/OAK-4863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020985#comment-16020985
]
Marcel Reutegger edited comment on OAK-4863 at 12/11/17 10:35 AM:
------------------------------------------------------------------
trunk: [r1762825|http://svn.apache.org/r1762825]
1.4: [r1795892|http://svn.apache.org/r1795892]
1.2: [r1817760|http://svn.apache.org/r1817760]
was (Author: reschke):
trunk: [r1762825|http://svn.apache.org/r1762825]
1.4: [r1795892|http://svn.apache.org/r1795892]
> 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: candidate_oak_1_0, resilience
> Fix For: 1.5.11, 1.6.0, 1.4.16, 1.2.28
>
>
> 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.4.14#64029)
