[
https://issues.apache.org/jira/browse/OAK-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058302#comment-15058302
]
Laurie byrum commented on OAK-2472:
-----------------------------------
[~edivad] thanks for your response. So we have a couple of use cases where it
is highly expected that we can have multiple threads updating the same count.
We can either be optimistic and handle failures when there are conflicts (does
that work? if we set the increment in 2 different threads and then commit, does
something somewhere notice and handle it correctly?) or we can be pessimistic
and lock. Alternately, we saw in the docs and code that there were some plans
where not just oak:increment was recognized, but oak:increment-UUID was
recognized. In that case, we could have the different threads set different
oak:increment-UUIDs and it should all work.
What are we missing?
> Add support for atomic counters on cluster solutions
> ----------------------------------------------------
>
> Key: OAK-2472
> URL: https://issues.apache.org/jira/browse/OAK-2472
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.3.0
> Reporter: Davide Giannella
> Assignee: Davide Giannella
> Labels: scalability
> Fix For: 1.4
>
> Attachments: atomic-counter.md
>
>
> As of OAK-2220 we added support for atomic counters in a non-clustered
> situation.
> This ticket is about covering the clustered ones.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
