sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (Jira)" <j...@apache.org>
Subject [jira] [Updated] (SLING-8965) Avoid committing for each skipped package
Date Wed, 12 Feb 2020 09:22:00 GMT

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

Christian Schneider updated SLING-8965:
---------------------------------------
    Fix Version/s: Content Distribution Journal Core 0.1.8

> Avoid committing for each skipped package 
> ------------------------------------------
>
>                 Key: SLING-8965
>                 URL: https://issues.apache.org/jira/browse/SLING-8965
>             Project: Sling
>          Issue Type: Bug
>          Components: Content Distribution
>            Reporter: Timothee Maret
>            Assignee: Christian Schneider
>            Priority: Major
>             Fix For: Content Distribution Journal Core 0.1.8
>
>
> With the SLING-8908 change, we ensure that all package messages (even skipped ones) are
marked as processed. By design, we mark processed package by committing to the local repository.
Committing to the repository is not cheap and we should minimise it. For setups that generate
a lot of skipped packages such as A) multiple farms support with multiple consumer agents
or B) multi-region deployments with varying latencies, the amount of commits will increase
even more.
> To reduce the commits, we should either redo SLING-8908 such that skipped offsets are
kept in memory or simply only commit skipped packages as aggregates (e.g. 1 commits for 10
skipped packages).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message