Carsten Ziegeler created SLING-2830:
---------------------------------------
Summary: Discontinue per job configurations for queue processing
Key: SLING-2830
URL: https://issues.apache.org/jira/browse/SLING-2830
Project: Sling
Issue Type: Improvement
Components: Extensions
Affects Versions: Extensions Event 3.1.4
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
Fix For: Extensions Event 3.1.6
The configuration of job handling is usually done through queue configurations.
These queues are assigned to one or more job topic and have different
characteristics like if these jobs can be processed in parallel, how often a
job should be retried, delay between retries etc. The queue's are configured
globally through OSGi ConfigAdmin and are therefore the same on all cluster
nodes.
When we started with the job handling, we didn't have this configuration, so
each and every job contained this whole information as properties of the job
itself - which clearly is a maintenance nightmare but can also lead to funny
situations where two jobs with the same topic contain different configurations
(e.g. one allowing parallel processing while the other does not).
With the introduction of the queue configurations, we already reduced the per
job configuration possibilities and in some cases these are already ignored.
For the new version I plan to discontinue the per job configuration of queue's
as it is simply not worth the effort to support it. And having a single truth
of queue configurations makes maintenance and troubleshooting way easier.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
