You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Davide Giannella (JIRA)" <ji...@apache.org> on 2016/01/11 09:18:39 UTC
[jira] [Commented] (OAK-2472) Add support for atomic counters on
cluster solutions
[ https://issues.apache.org/jira/browse/OAK-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091588#comment-15091588 ]
Davide Giannella commented on OAK-2472:
---------------------------------------
Latest update from Friday evening. If I go debug the UT, allowing
therefore more time between each step, for a total of 4 updates (2
updates on each of the 2 cluster nodes), you can see that only 4
updates are issued, get rescheduled some times and complete
successfully.
The same code, with the same conditions, run without any interruptions
gets into a sort-of loop re-creating over and over new tasks.
/cc [~mduerig], [~mreutegg]
> 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, 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)