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 2015/02/03 11:05:35 UTC
[jira] [Updated] (OAK-2220) Support for atomic counters
(non-clustered)
[ https://issues.apache.org/jira/browse/OAK-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davide Giannella updated OAK-2220:
----------------------------------
Summary: Support for atomic counters (non-clustered) (was: Support for atomic counters)
> Support for atomic counters (non-clustered)
> -------------------------------------------
>
> Key: OAK-2220
> URL: https://issues.apache.org/jira/browse/OAK-2220
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: core
> Reporter: Michael Dürig
> Assignee: Davide Giannella
> Fix For: 1.1.6
>
> Attachments: oak-atomic-counter.md
>
>
> For several use cases (think +1/-1 votes on forum posts) it would be good to have some basic support for atomic counters in Oak. Such counters must:
> # correctly reflect increments/decrements by integral parts across threads / cluster nodes,
> # exhibit some well defined consistency characteristics amongst each other,
> # not require cluster wide coordination.
> 1. is required so in the forum post example the correct number of votes is recorded for each post.
> 2. is important so in the forum post example sorting by votes results in the correct order.
> 3. is important as global cluster synchronisation run contrary to out overall scalability goals.
> Additionally such counters should allow the user to trade off the consistency characteristics from 2 for availability. I.e. scarifying some availability results in hight consistency.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)