cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Thompson (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-8446) Lost writes when using lightweight transactions
Date Tue, 09 Dec 2014 18:41:13 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-8446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Philip Thompson updated CASSANDRA-8446:
---------------------------------------
    Reproduced In: 2.1.2
    Fix Version/s: 2.1.3

> Lost writes when using lightweight transactions
> -----------------------------------------------
>
>                 Key: CASSANDRA-8446
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8446
>             Project: Cassandra
>          Issue Type: Bug
>          Components: API, Core
>         Environment: Cassandra 2.1.2 on Java(TM) SE Runtime Environment (build 1.7.0_65-b17)
>            Reporter: Jochen Zeischka
>             Fix For: 2.1.3
>
>
> There's a serious problem when using lightweight transactions. Whenever th cluster gets
any load, write timeout exceptions start to occur and the client has no way to know whether
the write actually succeeded or not.
> I a simple test (https://gist.github.com/anonymous/4c83f2962b57fce4c3df) this results
in large percentages of lost writes (0 - 50%, depending on the load).
> The problem was described in https://stackoverflow.com/questions/27313360/how-can-we-avoid-losing-writes-when-using-lightweight-transactions-cas-in-cass



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message