Nodetool repair inconsistencies

I am running a 3 node cluster of 3.0.6 instances and encountered an error when running nodetool compact. I then ran nodetool repair. No errors were returned. I then attempted to run nodetool compact again, but received the same error so the repair made no correction and reported no errors. After

Re: Cassandra 3.6: Compaction/Write Requests fail with org.xerial.snappy.SnappyError: [NOT_A_DIRECT_BUFFER] destination is not a direct buffer

I also found CASSANDRA-9548, "Doing a bit more digging into this, the SnappyCompressor does only support OFF_HEAP buffers.", however I already am using offheap_buffers. I also got this error with offheap_objects. On Tue, Jun 7, 2016 at 4:58 PM, Nimi Wariboko Jr wrote: >

Re: Change authorization from AllowAllAuthorizer to CassandraAuthorizer

Hello Sean, Recently I tried to enable Authentication on a existing cluster, I have see the below behaviour. (Clients already have the credentials and 3 node C* cluster) cluster 1 - Enabled Authentication on node1 by adding iptable rules (so that client will not communicate to this node) and I

Cassandra 3.6: Compaction/Write Requests fail with org.xerial.snappy.SnappyError: [NOT_A_DIRECT_BUFFER] destination is not a direct buffer

Has anyone seen this issue since upgrading to 3.6? I don't have a good idea what is going on yet, as my logs have just been spewing the following error. WARN [SharedPool-Worker-174] 2016-06-07 16:54:07,651 AbstractLocalAwareExecutorService.java:169 - Uncaught exception on thread

Can you enable Thrift on a node and still connect remotely to it using CQL/port 9042?

Hello, I have a question. I have changed the Cassandra driver (3.0.0) so we can connect to and query two nodes (Cassandra 3.2.1), the local one and a remote node, using the driver's native protocol (CQL, port 9042). But it seems that when I enable Thrift in cassandra.yaml (start_rpc=true, port

Re: Lightweight Transactions during datacenter outage

You can set the serial_consistency_level to LOCAL_SERIAL to tolerate a DC failure: http://datastax.github.io/python-driver/api/cassandra/query.html#cassandra.query.Statement.serial_consistency_level. It defaults to SERIAL, which ignores DCs. On Tue, Jun 7, 2016 at 12:26 PM, Jeronimo de A. Barros

Re: Unable to use native library in C* trigger

My guess would be it’s due to the UDF sandbox whitelist/blacklist ( https://github.com/apache/cassandra/blob/5288d434b3b559c7006fa001a2dc56f4f4b2e2c3/src/java/org/apache/cassandra/cql3/functions/UDFunction.java ). As far as I’m aware there is no way current of avoiding this (other than

Re: Change authorization from AllowAllAuthorizer to CassandraAuthorizer

Thank you, Sean! Felipe Esteves Tecnologia felipe.este...@b2wdigital.com Tel.: (21) 3504-7162 ramal 57162 Skype: felipe2esteves 2016-06-07 14:20 GMT-03:00 : > I answered a similar question here: > >

Lightweight Transactions during datacenter outage

Hi, I have a cluster spreaded among 2 datacenters (DC1 and DC2), two server on each DC and I have a keyspace with NetworkTopologyStrategy (DC1:2 and DC2:2) with the following table: CREATE TABLE test ( k1 int, k2 timeuuid, PRIMARY KEY ((k1), k2) ) WITH CLUSTERING ORDER BY (k2 DESC) During

RE: Change authorization from AllowAllAuthorizer to CassandraAuthorizer

I answered a similar question here: https://groups.google.com/forum/#!topic/nosql-databases/lLBebUCjD8Y Sean Durity – Lead Cassandra Admin From: Felipe Esteves [mailto:felipe.este...@b2wdigital.com] Sent: Tuesday, June 07, 2016 12:07 PM To: user@cassandra.apache.org Subject: Change

Change authorization from AllowAllAuthorizer to CassandraAuthorizer

Hi guys, I have a Cassandra 2.1.8 Community cluster running with AllowAllAuthorizer and have to change it, so I can implement permissions in different users. As I've checked in the docs, seems like a simple change, from AllowAllAuthorizer to CassandraAuthorizer in cassandra.yaml. However, I'm a

Re: Subscribe to Cassandra Commit Log

> > is there any documentation for this feature > I'm not sure what the state of documentation is for Change Data Capture. The best docs may be the design document linked in the comments on the ticket, which I think is current. > perhaps what I am looking for is the reading the commit logs in

Unable to use native library in C* trigger

Hi, all, I am attempting write a trigger that depends on a native library. The library is successfully loaded by the JVM (so the java.library.path should not be the issue - I just have the jnilib in lib/sigar-bin for now) but any call to its methods result in a java.lang.UnsatisfiedLinkError.

Re: Subscribe to Cassandra Commit Log

Hi Jim, Thanks for highlighting the updates, well is there any documentation for this feature, perhaps what I am looking for is the reading the commit logs in real time to capture all the updates fired to the corresponding tables. Also any update on the tentative release of this branch? Thanks!

Re: [Marketing Mail] [Marketing Mail] Cassandra 2.1: Snapshot data changing while transferring

Hi there, just for your information: I found out whats actually happening. It's not the file content which is changing. It's the number of hard links to the files which is changing because during the tar is running, some incremental backups are created. In that case, tar gives a warning that

How to remove 'compact storage' attribute?

Hi, All, Since the Astyanax client has been EOL, we are considering to migrate to Datastax java client in our product. One thing I notice is that the CFs created by Astyanax have 'compact storage' attribute which prevent us from using some new features provided by CQL such as secondary index.