[
https://issues.apache.org/jira/browse/CURATOR-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632947#comment-14632947
]
ASF GitHub Bot commented on CURATOR-225:
----------------------------------------
Github user Randgalt commented on the pull request:
https://github.com/apache/curator/pull/85#issuecomment-122711711
Maybe we should have REQUEUE attempt to put it back where it was instead of
adding a new mode.
> 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)
