[
https://issues.apache.org/jira/browse/SLING-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-1002.
-------------------------------------
Resolution: Fixed
On startup, the jobs are now loaded in a separate background thread from the
repository. This ensures that the job handler is immediately available and only
a configurable amount
of jobs is loaded in one batch from the repository.
> Reduce memory consumption and improve startup behaviour of the job handler
> --------------------------------------------------------------------------
>
> Key: SLING-1002
> URL: https://issues.apache.org/jira/browse/SLING-1002
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: Extensions Event 2.0.4
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Extensions Event 2.2.0
>
>
> Currently the job handler holds all received jobs in memory until the job has
> been processed completly. In addition on startup all unprocessed jobs are
> loaded from the repository.
> If for example thousands of jobs are unprocessed in the repository and a new
> instance is started (or restarted) all these events are first load into
> memory and then put into the queue.
> It would be better to have a fixed max size for the in memory queue - and
> check the repository from time to time for unprocessed jobs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
