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 "Julian Reschke (JIRA)" <ji...@apache.org> on 2016/10/24 12:51:58 UTC
[jira] [Commented] (OAK-3975) Change DELETE_BATCH_SIZE to 100 (from
450), and make it configurable
[ https://issues.apache.org/jira/browse/OAK-3975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15601897#comment-15601897 ]
Julian Reschke commented on OAK-3975:
-------------------------------------
FWIW, inserting a parameter *between* an age value and the corresponding time unit is very confusing:
{noformat}
public int gc(long maxRevisionAge, int batchSize, TimeUnit unit) { ... }
{noformat}
> Change DELETE_BATCH_SIZE to 100 (from 450), and make it configurable
> --------------------------------------------------------------------
>
> Key: OAK-3975
> URL: https://issues.apache.org/jira/browse/OAK-3975
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: documentmk
> Affects Versions: 1.3.14
> Reporter: Stefan Egli
> Assignee: Stefan Egli
> Priority: Critical
> Fix For: 1.4, 1.3.16
>
>
> When large journal entries (with large {{_c}} values) exist, the journal gc can get into trouble as it currently loads 450 of them ({{DELETE_BATCH_SIZE}}). In order to improve this situation without having to fix OAK-3001 we can reduce the default of 450 to 100.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)