You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "Jordan Zimmerman (JIRA)" <ji...@apache.org> on 2016/03/29 16:08:25 UTC
[jira] [Closed] (CURATOR-225) Add a new mode ErrorMode.KEEP
[ https://issues.apache.org/jira/browse/CURATOR-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jordan Zimmerman closed CURATOR-225.
------------------------------------
Resolution: Not A Problem
Fix Version/s: (was: awaiting-response)
> 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: Minor
> 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)