Return-Path: X-Original-To: apmail-curator-dev-archive@minotaur.apache.org Delivered-To: apmail-curator-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 04493117A3 for ; Tue, 8 Jul 2014 01:33:35 +0000 (UTC) Received: (qmail 79680 invoked by uid 500); 8 Jul 2014 01:33:34 -0000 Delivered-To: apmail-curator-dev-archive@curator.apache.org Received: (qmail 79642 invoked by uid 500); 8 Jul 2014 01:33:34 -0000 Mailing-List: contact dev-help@curator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@curator.apache.org Delivered-To: mailing list dev@curator.apache.org Received: (qmail 79562 invoked by uid 99); 8 Jul 2014 01:33:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Jul 2014 01:33:34 +0000 Date: Tue, 8 Jul 2014 01:33:34 +0000 (UTC) From: "Cameron McKenzie (JIRA)" To: dev@curator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Work started] (CURATOR-116) Ordering of delayed distributed queue is inconsistent MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CURATOR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CURATOR-116 started by Cameron McKenzie. > Ordering of delayed distributed queue is inconsistent > ----------------------------------------------------- > > Key: CURATOR-116 > URL: https://issues.apache.org/jira/browse/CURATOR-116 > Project: Apache Curator > Issue Type: Bug > Components: Recipes > Affects Versions: 2.5.0 > Reporter: Cameron McKenzie > Assignee: Cameron McKenzie > Priority: Minor > Labels: DelayedDistributedQueue, recipes > > 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. -- This message was sent by Atlassian JIRA (v6.2#6252)