[
https://issues.apache.org/jira/browse/CURATOR-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Никита Соколов updated CURATOR-605:
-----------------------------------
Description:
The is similar to one described here:
https://issues.apache.org/jira/browse/CURATOR-537
https://issues.apache.org/jira/browse/CURATOR-542
There is no way for consumer to check if the lock still holds. It could be
solved by sharing a transactional CheckOp for lockNodePath with a consumer, so
he could consume the message transactionally.
was:
The is similar to one described here –
https://issues.apache.org/jira/browse/CURATOR-542
There is no way for consumer to check if the lock still holds. It could be
solved by sharing a transactional CheckOp for lockNodePath with a consumer, so
he could consume the message transactionally.
> DistributedQueue#processWithLockSafety can give a message to two consumers if
> first consumer session dies
> ---------------------------------------------------------------------------------------------------------
>
> Key: CURATOR-605
> URL: https://issues.apache.org/jira/browse/CURATOR-605
> Project: Apache Curator
> Issue Type: Bug
> Reporter: Никита Соколов
> Assignee: Jordan Zimmerman
> Priority: Major
>
> The is similar to one described here:
> https://issues.apache.org/jira/browse/CURATOR-537
> https://issues.apache.org/jira/browse/CURATOR-542
> There is no way for consumer to check if the lock still holds. It could be
> solved by sharing a transactional CheckOp for lockNodePath with a consumer,
> so he could consume the message transactionally.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
