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 "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2017/12/11 10:35:00 UTC

[jira] [Updated] (OAK-4863) Reduce query batch size for deleted documents

     [ https://issues.apache.org/jira/browse/OAK-4863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Reutegger updated OAK-4863:
----------------------------------
           Labels: candidate_oak_1_0 resilience  (was: candidate_oak_1_0 candidate_oak_1_2 resilience)
    Fix Version/s: 1.2.28

> 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)