RE: Re[6]: Modify keyspace replication strategy and rebalance the nodes

2017-09-19 Thread Myron A. Semack
be satisfied)? Sincerely, Myron A. Semack From: Jeff Jirsa [mailto:jji...@gmail.com] Sent: Monday, September 18, 2017 6:02 PM To: cassandra <user@cassandra.apache.org> Subject: Re: Re[6]: Modify keyspace replication strategy and rebalance the nodes Using CL:ALL basically forces you to

RE: Re[6]: Modify keyspace replication strategy and rebalance the nodes

2017-09-18 Thread Myron A. Semack
How would setting the consistency to ALL help? Wouldn’t that just cause EVERY read/write to fail after the ALTER until the repair is complete? Sincerely, Myron A. Semack From: Jeff Jirsa [mailto:jji...@gmail.com] Sent: Monday, September 18, 2017 2:42 PM To: user@cassandra.apache.org Subject

RE: Attempted to write commit log entry for unrecognized table

2017-08-16 Thread Myron A. Semack
Restarting the Cassandra service resolved this issue. Thanks for your advice! Sincerely, Myron A. Semack From: kurt greaves [mailto:k...@instaclustr.com] Sent: Tuesday, August 15, 2017 6:10 PM To: User <user@cassandra.apache.org> Subject: Re: Attempted to write commit log

Attempted to write commit log entry for unrecognized table

2017-08-15 Thread Myron A. Semack
guidance on how to deal with this error. Is there a way to recover from this error? (Preferably without terminating and rebuilding the node.) Sincerely, Myron A. Semack - To unsubscribe, e-mail: user-unsubscr