[
https://issues.apache.org/jira/browse/ZOOKEEPER-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16486931#comment-16486931
]
wayne edited comment on ZOOKEEPER-3049 at 5/23/18 8:59 AM:
-----------------------------------------------------------
[~lvfangmin] does this mean that the multiple ops would be executed atomically
on a same node? so any clients would see either the staled data (2, 4) or the
new data (3, 5), they shouldn't be seeing (2,5) or (3, 4)? If so, could you
give a pointer of the source code that synchronize the multiple ops?
was (Author: wayne sun):
[~lvfangmin] does this mean that the multiple ops would be executed atomically
on a same node? so any clients would see either the staled data (2, 4) or the
new data (3, 5), they shouldn't be seeing (2,5) or (3, 4)?
> would zookeeper transaction(multi) block the concurrent read?
> -------------------------------------------------------------
>
> Key: ZOOKEEPER-3049
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3049
> Project: ZooKeeper
> Issue Type: Wish
> Components: documentation
> Reporter: wayne
> Priority: Major
>
> For instance, the original data for znode1 and znode2 are 2 and 4
> respectively. I want to perform increment operations over them. Finally, I
> would get (3, 5) for znode1 and znode2. In order to keep atomicity, I used
> multi() api. Is there any possibility that any clients could read (3, 4)
> concurrently? That is, the read happened after znode1++ and before znode2++?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
