[
https://issues.apache.org/jira/browse/OAK-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091981#comment-15091981
]
Davide Giannella commented on OAK-2472:
---------------------------------------
[~mreutegg] it seems your suspect was right. What's happening is:
- the first 4 threads start
- they get processed by the counter and scheduled
- as soon as it starts processing counter from "different cluster nodes" it
gets a Collision
- DNSB suspend and resume later on
- a new counter is processed from scratch generating a new scheduled task that
will add to the conflicts
ideas on possible solutions?
> 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: OAK-2472-failure-1452511772.log.gz,
> OAK-2472-success-1452511511.log.gz, atomic-counter.md, oak-1452185608.log.gz,
> oak-1452268140.log.gz
>
>
> 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)
