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 "Alex Parvulescu (JIRA)" <ji...@apache.org> on 2015/02/19 15:56:11 UTC
[jira] [Commented] (OAK-2535) TARMK Cold Standby allow cleanup on
standby instance
[ https://issues.apache.org/jira/browse/OAK-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14327597#comment-14327597 ]
Alex Parvulescu commented on OAK-2535:
--------------------------------------
rev http://svn.apache.org/r1660903
- added cleanup operation, also exposed via JMX
- added automatic cleanup call once the sync size > 25% of the store to account for the compaction scenario
> TARMK Cold Standby allow cleanup on standby instance
> ----------------------------------------------------
>
> Key: OAK-2535
> URL: https://issues.apache.org/jira/browse/OAK-2535
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segmentmk
> Reporter: Alex Parvulescu
> Assignee: Alex Parvulescu
> Fix For: 1.0.12, 1.1.7
>
>
> The standby instance size can increase due to the continuous sync process, and there's currently no way to run a cleanup operation.
> This only gets worse when running compaction on the primary, the standby finds a new head state and starts pulling in all the changes effectively doubling (size = old standby size + primary size) the size of the store.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)