curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Drob (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-225) Add a new mode ErrorMode.KEEP
Date Wed, 24 Jun 2015 18:10:05 GMT

    [ https://issues.apache.org/jira/browse/CURATOR-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14599862#comment-14599862
] 

Mike Drob commented on CURATOR-225:
-----------------------------------

Is the intent for the consumer to leave the error'd item in the queue, and then move on to
the next item? Or to keep retrying on the same item until it succeeds, and then moving on
to the next?

> Add a new mode ErrorMode.KEEP
> -----------------------------
>
>                 Key: CURATOR-225
>                 URL: https://issues.apache.org/jira/browse/CURATOR-225
>             Project: Apache Curator
>          Issue Type: New Feature
>          Components: Framework
>    Affects Versions: 2.8.0
>         Environment: Windows 7/Java 8
>            Reporter: Zhihong Zhang
>            Priority: Critical
>              Labels: curator, locking, queue
>
> When locking is used and consumer throws exception, there are currently 2 modes, REQUEUE
and DELETE.  In our use-cases, the items in the queue need to keep in the same FIFO order,
even in case of the error. A 3rd mode is needed to keep the queue order intact.



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

Mime
View raw message