[CURATOR-116] Ordering of delayed distributed queue is inconsistent

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.5.0
• Fix Version/s: 2.6.0
• Component/s: Recipes
• Labels: DelayedDistributedQueue recipes
• Assignee: Cam McKenzie
• Reporter: Cam McKenzie
• Created: 24/Jun/14 05:36
• Updated: 10/May/23 15:01
• Resolved: 08/Jul/14 01:35

Description

The ordering in which elements in the delayed distributed queue are processed is inconsistent. Only elements that have reached their expiry time are processed, but their actual order is not deterministic due to the logic used for sorting. The current time is used during the sorting process, so if an element becomes ready for processing half way through the sort, the order is not deterministic.

The current time should be determined at the start of the sort process, and this point in time used for all comparisons.

I believe this is the root cause for CURATOR-115 also, but I cannot reproduce CURATOR-115, so I have raised this as a separate defect.

Issue Links

• fixes: CURATOR-115 delayeddistributedqueue failed to sort children
• is related to: CURATOR-115 delayeddistributedqueue failed to sort children
• relates to: CURATOR-115 delayeddistributedqueue failed to sort children