RE: Not serving read requests while running nodetool repair

Hi Jeff, thanks for the info. Hoped that nodetool provides an option for that. We will go with the temporary QUORUM approach for now. Thanks again. Thomas From: Jeff Jirsa [mailto:jji...@gmail.com] Sent: Mittwoch, 18. Oktober 2017 15:46 To: user@cassandra.apache.org Subject: Re: Not serving re

Re: UTF8 error

If you can get into one of the nodes, ŒSELECT table_name from system_schema.tables¹ and see if any of the data looks corrupt (here¹s the block of code executing, it¹s loading all of the tables by name - https://github.com/apache/cassandra/blob/cassandra-3.0.9/src/java/org/apache /cassandra/schema/S

Re: UTF8 error

Thanks Jeffery, will consider upgrading to 3.0.15. issue is happening again and again and it's across the nodes. when we do the rolling bounce also this issue is happening. Thanks, Suresh. On Wed, Oct 18, 2017 at 11:33 PM, Jeffrey Jirsa wrote: > Is it only one node, or all of them? The stack

Re: UTF8 error

Is it only one node, or all of them? The stack says it¹s in loading all of the other schema data from disk, so if it¹s only one instance in the cluster, you could probably recover by removing the schema, it¹ll boot and pull schema from the rest of the cluster. Alternatively, you could pretend like

Re: UTF8 error

Thanks Michael. we don't have any data in the Column Famility. we are getting the error after creating the schema and CF's using the cqlsh to connect to cluster. node is going down and not able to connect it and getting the above error. Thanks, Suresh On Wed, Oct 18, 2017 at 10:44 PM, Michael S

Re: UTF8 error

On 10/18/2017 09:02 PM, Suresh Babu Mallampati wrote: > cqlsh: Connection error: ('Unable to connect to any servers', > {'127.0.0.1': UnicodeDecodeError('utf8', '\x00\x00\x00\xf0\x8f\x0e', 3, > 5, 'unexpected end of data')}) This does appear to be invalid UTF-8, so the error is valid. Perhaps you

UTF8 error

Using Cassandra 3.0.9 version I am getting the below error: cqlsh: Connection error: ('Unable to connect to any servers', {'127.0.0.1': UnicodeDecodeError('utf8', '\x00\x00\x00\xf0\x8f\x0e', 3, 5, 'unexpected end of data')}) ERROR [main] 2017-10-17 11:56:17,384 o.a.c.s.CassandraDaemon - Except

Re: cassandra-stress w/ DC aware

I figured it out ... cassandra-stress user profile=myprofile.yaml cl=local_quorum node= ... On Wednesday, October 18, 2017, 12:07:35 PM PDT, Subroto Barua wrote: is it possible to run cassandra-stress against a specific DC w/ user yaml file?  there is an option w/o yaml, but I am not

Re: 3.0 is slower than 2.2 ?

There were some perf regressions from 8099 (storage engine rewrite) that were addressed around 3.10 https://issues.apache.org/jira/browse/CASSANDRA-12269 https://issues.apache.org/jira/browse/CASSANDRA-9766 To pick up those fixes, you'd want to benchmark 3.11.1 instead of 3.0.15 On Tue, Oct 17

cassandra-stress w/ DC aware

is it possible to run cassandra-stress against a specific DC w/ user yaml file?  there is an option w/o yaml, but I am not sure i can do the same with USER option.. cassandra: 3.0.12 thanks! Subroto

Re: Not serving read requests while running nodetool repair

You can accomplish this by manually tweaking the values in the dynamic snitch mbean so other nodes won’t select it for reads -- Jeff Jirsa > On Oct 18, 2017, at 3:24 AM, Steinmaurer, Thomas > wrote: > > Hi Nicolas, > > newly bootstrapping is not really an option, I think. > > I hoped th

RE: Not serving read requests while running nodetool repair

Hi Nicolas, newly bootstrapping is not really an option, I think. I hoped there might be a mode (perhaps there is, but haven’t found it yet) where a node might not actively participate in read requests but still writing newly arriving data during a repair or whatever maintenance task one thinks

Re: Restore cassandra snapshots

Hi Jean, Thank you very much for verifying the steps. Regards. On Wed, Oct 18, 2017 at 11:52 AM, Jean Carlo wrote: > Hi Pradeep, > > Because you use sstableloader, you don't need to restore de system > keyspace. > > Your procedure is correct to me. > > Best regards > > On Oct 18, 2017 4:22 AM,

Re: Not serving read requests while running nodetool repair

Hi Thomas, AFAIK temporarily reading at LOCAL_QUORUM/QUORUM until nodetool repair is finished is the way to go. You can still disable binary/thrift on the node to "protect" it from acting as a coordinator, and complete its repair quietly, but I'm not sure that would make such a huge difference in

Re: Looking for advice and assistance upgrading from Cassandra 1.2.9

Hi David, Last time I did such an upgrade, I got stuck in 2.1.x because of OpsCenter 5.2 : http://docs.datastax.com/en/landing_page/doc/landing_page/compatibility.html#compatibility__opsc-compatibility . This might have change since, but I do not think C* 2.2 will work with OpsCenter 5.2 If you a