[jira] [Updated] (OAK-5029) Use head GC generation number to trigger cleanup on standby instance
[
https://issues.apache.org/jira/browse/OAK-5029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothee Maret updated OAK-5029:
Attachment: OAK-5029.patch
Attaching a svn compatible patch, otherwise available at
https://github.com/tmaret/jackrabbit-oak/commit/aa421e549b5b150d56ebd32a6534fe2a432e2fa1
The patch does
1. Change the mechanism to trigger cleanup on standby instance, use the head
segment gc generation number
2. Update the {{standby.autoclean}} OSGI description to reflect the change
> Use head GC generation number to trigger cleanup on standby instance
> -
>
> Key: OAK-5029
> URL: https://issues.apache.org/jira/browse/OAK-5029
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
>Affects Versions: Segment Tar 0.0.16
>Reporter: Timothee Maret
>Assignee: Timothee Maret
> Attachments: OAK-5029.patch
>
>
> With {{oak-segment-tar}}, the trigger for running {{cleanup}} on the standby
> instance could be determined by the GC generation number of the head which is
> bound to increase every time a cleanup is ran.
> {code}
> fileStore.getHead().getRecordId().getSegment().getGcGeneration();
> {code}
> The current trigger mechanism consists of detecting a 25% size increase over
> a client cycle (typ. 5 sec).
> This would be dropped in favor of the new detection mechanism.
> The auto-compaction mode would remain configurable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OAK-5029) Use head GC generation number to trigger cleanup on standby instance
[
https://issues.apache.org/jira/browse/OAK-5029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothee Maret updated OAK-5029:
Flags: Patch
> Use head GC generation number to trigger cleanup on standby instance
> -
>
> Key: OAK-5029
> URL: https://issues.apache.org/jira/browse/OAK-5029
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
>Affects Versions: Segment Tar 0.0.16
>Reporter: Timothee Maret
>Assignee: Timothee Maret
> Attachments: OAK-5029.patch
>
>
> With {{oak-segment-tar}}, the trigger for running {{cleanup}} on the standby
> instance could be determined by the GC generation number of the head which is
> bound to increase every time a cleanup is ran.
> {code}
> fileStore.getHead().getRecordId().getSegment().getGcGeneration();
> {code}
> The current trigger mechanism consists of detecting a 25% size increase over
> a client cycle (typ. 5 sec).
> This would be dropped in favor of the new detection mechanism.
> The auto-compaction mode would remain configurable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OAK-5029) Use head GC generation number to trigger cleanup on standby instance
[
https://issues.apache.org/jira/browse/OAK-5029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothee Maret updated OAK-5029:
Description:
With {{oak-segment-tar}}, the trigger for running {{cleanup}} on the standby
instance could be determined by the GC generation number of the head which is
bound to increase every time a cleanup is ran.
{code}
fileStore.getHead().getRecordId().getSegment().getGcGeneration();
{code}
The current trigger mechanism consists of detecting a 25% size increase over a
client cycle (typ. 5 sec).
This would be dropped in favor of the new detection mechanism.
The auto-compaction mode would remain configurable.
was:
With {{oak-segment-tar}}, the trigger for running {{cleanup}} on the standby
instance could be determined by the GC generation number of the head which is
bound to increase every time a cleanup is ran.
{code}
fileStore.getHead().getRecordId().getSegment().getGcGeneration();
{code}
> Use head GC generation number to trigger cleanup on standby instance
> -
>
> Key: OAK-5029
> URL: https://issues.apache.org/jira/browse/OAK-5029
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
>Affects Versions: Segment Tar 0.0.16
>Reporter: Timothee Maret
>Assignee: Timothee Maret
>
> With {{oak-segment-tar}}, the trigger for running {{cleanup}} on the standby
> instance could be determined by the GC generation number of the head which is
> bound to increase every time a cleanup is ran.
> {code}
> fileStore.getHead().getRecordId().getSegment().getGcGeneration();
> {code}
> The current trigger mechanism consists of detecting a 25% size increase over
> a client cycle (typ. 5 sec).
> This would be dropped in favor of the new detection mechanism.
> The auto-compaction mode would remain configurable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
