sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (SLING-4096) Jobs might stay unprocessed when topology changes
Date Sat, 01 Nov 2014 15:06:35 GMT

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

Carsten Ziegeler closed SLING-4096.
-----------------------------------

> Jobs might stay unprocessed when topology changes
> -------------------------------------------------
>
>                 Key: SLING-4096
>                 URL: https://issues.apache.org/jira/browse/SLING-4096
>             Project: Sling
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: Event 3.4.0
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Blocker
>             Fix For: Event 3.4.2
>
>
> When the topology changes, the job manager stores all jobs in the unassigned area - which
is correct.
> When the topology is established, first a maintenance task moves the jobs out of that
area and assigns it to instances, then the job manager is informed about the change of the
topology. If the job manager is adding jobs in between, these stay in the unassigned area.
> On the next change of the topology they get picked up though



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message