james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Charles (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAILBOX-209) A data race is possible with Cassandra modseq generation
Date Sun, 08 Mar 2015 14:35:38 GMT

    [ https://issues.apache.org/jira/browse/MAILBOX-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352063#comment-14352063

Eric Charles commented on MAILBOX-209:

Can you rebase on latest trunk (uploaded patch does not apply here)? Thx.

> A data race is possible with Cassandra modseq generation
> --------------------------------------------------------
>                 Key: MAILBOX-209
>                 URL: https://issues.apache.org/jira/browse/MAILBOX-209
>             Project: James Mailbox
>          Issue Type: Bug
>            Reporter: Tellier Benoit
>         Attachments: fix_cassandra_modseq_provider.patch
> The Cassandra mailbox implementation proceed as follow to increase the modseq :
>  - a first call to Cassandra to increase the modseq value for a given mailbox
>  - a second call allow us to retrieve the current value.
> Note that you can not do it in a single call...
> In a distributed environment, imagine that :
>  - for a mailbox the current modseq is n
>  - server A increments modseq. Modseq is n+1
>  - server B increments modseq. Modseq is n+2
>  - server A and B then retrieve the modseq value and have a duplicated modseq : they
for instance both can assign n+2 value to a different message.
> The problem can be solved using conditionnal updates with lightweight transactions.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message