Re: Handling uncommitted paxos state

2016-02-25 Thread Robert Coli
On Thu, Feb 25, 2016 at 1:23 AM, Nicholas Wilson < nicholas.wil...@realvnc.com> wrote: > If a WriteTimeoutException with WriteType.SIMPLE is thrown for a CAS > write, that means that the paxos phase was successful, but the data > couldn't be committed during the final 'commit/reset' phase. On the

Re: Handling uncommitted paxos state

2016-02-25 Thread Carl Yeksigian
The paxos state is written to a system table (system.paxos) on each of the paxos coordinators, so it goes through the normal write path, including persisting to the log and being stored in a memtable until being flushed to disk. As such, the state can survive restarts. These states are not treated

Handling uncommitted paxos state

2016-02-25 Thread Nicholas Wilson
Hi, I have some questions about the behaviour of 'uncommitted paxos state', as described here: http://www.datastax.com/dev/blog/cassandra-error-handling-done-right If a WriteTimeoutException with WriteType.SIMPLE is thrown for a CAS write, that means that the paxos phase was successful, but