Re: Read operation can read uncommitted data?

Tyler Thank you for your reply. I have 2 questions. Will the reads resume the CAS operation? Do the reads repair in-progress paxos writes in read/results phase too? According to the following article, when an UnavailableException or a WriteTimeoutException occur (propose or commit phase fail), r

Changing a cluster name

system.local uses local strategy . You need to update on all nodes . On 28 June 2016 at 14:51, Tyler Hobbs > wrote: > First, make sure that you call nodetool flush after modifying the system > table. That's probably why it's not surviving the restart. > > Second, I believe you will have to do t

Re: Read operation can read uncommitted data?

Reads at CL.SERIAL will complete any in-progress paxos writes, so the behavior you're seeing is expected. On Mon, Jun 27, 2016 at 1:55 AM, Yuji Ito wrote: > Hi, > > I'm testing Cassandra CAS operation. > > Can a read operation read uncommitted data which is being updated by CAS > in the followin

Re: Adding column to materialized view

Thanks Tyler. -J On Tue, Jun 28, 2016 at 3:48 PM, Tyler Hobbs wrote: > This is expected. It's something we plan to support, but it hasn't been > done yet: https://issues.apache.org/jira/browse/CASSANDRA-9736 > > On Mon, Jun 27, 2016 at 4:25 PM, Jason J. W. Williams < > jasonjwwilli...@gmail.co

Re: Changing a cluster name

First, make sure that you call nodetool flush after modifying the system table. That's probably why it's not surviving the restart. Second, I believe you will have to do this across all nodes and restart them at the same time. Otherwise, cluster name mismatches will prevent the nodes from commun

Re: Adding column to materialized view

This is expected. It's something we plan to support, but it hasn't been done yet: https://issues.apache.org/jira/browse/CASSANDRA-9736 On Mon, Jun 27, 2016 at 4:25 PM, Jason J. W. Williams < jasonjwwilli...@gmail.com> wrote: > Hey Guys, > > Running Cassandra 3.0.5. Needed to add a column to a ma

Motivation for a DHT ring

Hi all, Please, What is the motivation for choosing a DHT ring in cassandra? Why not use a normal parallel or distributed file system that supports replication? Thank you so much for clarification. Kind regards.

Re: Exception in logs using LCS .

1. Not necessarily data corruption, but it seems compaction is trying to write data in the wrong order most likely due to a temporary race condition/bug a la #9935, but since the compaction fails your original data is probably safe (you can try running scrub to verify/fix corruptions). 2. This is p

Exception in logs using LCS .

Hello, Recently we changed compaction strategy fora table to LCS from the default STCS. While bootstrapping a node , we are getting following Exception in the logs: ERROR [CompactionExecutor:81] 2016-05-11 13:48:54,694 CassandraDaemon.java (line 258) Exception in thread Thread[CompactionExecut

Re: C* 3.0.7 - Compactions pending after TRUNCATE

I am updating the following ticket https://issues.apache.org/jira/browse/CASSANDRA-12100 as I discover new bits. Regards, Stefano On Tue, Jun 28, 2016 at 9:37 AM, Stefano Ortolani wrote: > Hi all, > > I've just updated to C* 3.0.7, and I am now seeing some compactions > getting stuck: nodetool

C* 3.0.7 - Compactions pending after TRUNCATE

Hi all, I've just updated to C* 3.0.7, and I am now seeing some compactions getting stuck: nodetool compationstats has been showing the same output for the last 6 hours, and all compactions are stuck at 0.00% progress. What is interesting is that the stuck CFs have been truncated exactly 6 hours