curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhihong Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-225) Add a new mode ErrorMode.KEEP
Date Tue, 29 Mar 2016 14:01:25 GMT

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

Zhihong Zhang commented on CURATOR-225:
---------------------------------------

[~randgalt] I think we can close/ignore this ticket. I will see if I can remove the pull request.
We don't use Curator for this feature anymore. Our custom solution works great and I don't
really want touch it.


> 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
>             Fix For: awaiting-response
>
>
> 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