Re: INSERT ... IF NOT EXISTS with some nodes unavailable

Hello Mitchell, I think it is due to your replication factor, which, I assume, is 2 since you have only 2 nodes in the cluster. If you are using even number of nodes, Cassandra is impossible to run queries require QUORUM participants. So, I think you have to expand your cluster to 3 nodes and mak

Re: Paxos table gets larger when using 'IF NOT EXISTS'

12:51 GMT+09:00 Frederick Haebin Na : > Again, sorry for spamming. > > I found out that there is no delete query for system.paxos. (2.0.6 code > base, I'm using 2.0.7, tho.) > > Holy cow. > So, It does not get deleted? > Is this correct? > > Thanks. > >

Re: Paxos table gets larger when using 'IF NOT EXISTS'

Again, sorry for spamming. I found out that there is no delete query for system.paxos. (2.0.6 code base, I'm using 2.0.7, tho.) Holy cow. So, It does not get deleted? Is this correct? Thanks. Haebin 2014-06-03 12:07 GMT+09:00 Frederick Haebin Na : > Sorry for spamming, folks. >

Re: Paxos table gets larger when using 'IF NOT EXISTS'

Thanks. Haebin 2014-06-03 11:20 GMT+09:00 Frederick Haebin Na : > Sorry, I found out what are in the system.paxos. > > select * from system.paxos limit 1; > > | row_key | cf_id | in_porgress_ballot | most_recent_commit | > most_recent_commit_at | proposal | proposal_ballot | >

Re: Paxos table gets larger when using 'IF NOT EXISTS'

like this, please, share your experiences. Thank you. Haebin 2014-06-03 11:00 GMT+09:00 Frederick Haebin Na : > Hello all, > > We are trying to migrate data with 'INSERT IF NOT EXISTS' clause. > Yet, strange thing is that the system.paxos table gets larger like 100GB > w

Paxos table gets larger when using 'IF NOT EXISTS'

Hello all, We are trying to migrate data with 'INSERT IF NOT EXISTS' clause. Yet, strange thing is that the system.paxos table gets larger like 100GB which is equal to the size of the data table. Does anyone know what is happening here? What does system.paxos table store? Thank you. Haebin