[ https://issues.apache.org/jira/browse/CASSANDRA-8446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14239206#comment-14239206 ]
Jochen Zeischka commented on CASSANDRA-8446: -------------------------------------------- Might be interesting: we do not get write timeouts when using replication factor 2, but do get them with rep factor 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 > > 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)