jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OAK-4863) Reduce query batch size for deleted documents
Date Tue, 12 Dec 2017 07:59:00 GMT

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

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

> 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.5.11, 1.6.0, 1.4.16, 1.0.40, 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)

Mime
View raw message