[ https://issues.apache.org/jira/browse/SLING-10112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17368001#comment-17368001 ]
Timothee Maret commented on SLING-10112: ---------------------------------------- This approach has a flaw with cloud deployments that treat Sling instances as a cattle. In those deployments, each instances starts with a new slingId. Commands are sent to a specific subscriber agent identified by subSlingId and subAgentName. As a result, the command is not being picked up when the instance is replaced. We should revert this change given that SLING-10528 avoids the condition that required this change. > Distribution Queue can not be reliably cleared due to race condition > processing delete messages > ----------------------------------------------------------------------------------------------- > > Key: SLING-10112 > URL: https://issues.apache.org/jira/browse/SLING-10112 > Project: Sling > Issue Type: Improvement > Components: Content Distribution > Reporter: Christian Schneider > Assignee: Christian Schneider > Priority: Major > Fix For: Content Distribution Journal Core 0.1.18 > > > Replication queue can not be reliable cleared due to race condition with > processing the 'delete' messages. > If the first message is stuck during processing, the 'clear queue' signal > might never have effect on the subscriber. > A restart of the process does not help as the same situation might occur. -- This message was sent by Atlassian Jira (v8.3.4#803005)