[jira] [Updated] (SLING-12289) PackageStatusWatcher should ignore additional status for the same package
[ https://issues.apache.org/jira/browse/SLING-12289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider updated SLING-12289: Component/s: Content Distribution > PackageStatusWatcher should ignore additional status for the same package > - > > Key: SLING-12289 > URL: https://issues.apache.org/jira/browse/SLING-12289 > Project: Sling > Issue Type: Improvement > Components: Content Distribution >Reporter: Christian Schneider >Assignee: Christian Schneider >Priority: Major > Fix For: Content Distribution Journal Core 0.3.0 > > > If a second status message arrives when we already have a status stored > locally we should ignore the new status message. > This is to avoid that a restarted system after node store compaction works > with a different status than the running system. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-12289) PackageStatusWatcher should ignore additional status for the same package
[ https://issues.apache.org/jira/browse/SLING-12289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider updated SLING-12289: Description: If a second status message arrives when we already have a status stored locally we should ignore the new status message. This is to avoid that a restarted system after node store compaction works with a different status than the running system. was:If a second status message arrives when we already have a status stored locally we should ignore the new status message. > PackageStatusWatcher should ignore additional status for the same package > - > > Key: SLING-12289 > URL: https://issues.apache.org/jira/browse/SLING-12289 > Project: Sling > Issue Type: Improvement >Reporter: Christian Schneider >Assignee: Christian Schneider >Priority: Major > Fix For: Content Distribution Journal Core 0.3.0 > > > If a second status message arrives when we already have a status stored > locally we should ignore the new status message. > This is to avoid that a restarted system after node store compaction works > with a different status than the running system. -- This message was sent by Atlassian Jira (v8.20.10#820010)
