Re: Back to the futex()? :(

I noticed you have authentication enabled. Make sure you set the following: - the replication factor for the system_auth keyspace should equal the number of nodes - permissions_validity_in_ms is a permission cache timeout. If you are not doing dynamic permissions or creating/revoking frequently,

Re: [RELEASE] Apache Cassandra 3.3 released

No problem. Run it after you upgrade. On Tue, Feb 9, 2016 at 2:01 PM, Will Hayworth wrote: > Pardon my ignorance, Jake--should we run upgradesstables -a after or > before we install 3.3? > > Thanks! :) > > ___ >

Re: Back to the futex()? :(

I'm not surprised that when you profile cassandra you are seeing some lock contention, particularly given its SEDA architecture, as there is a lot of waiting that threads end up doing while requests make their way through the various stages. See

Re: [RELEASE] Apache Cassandra 3.3 released

Technically this is actually "a bug fix release[1] on the 3.x series" - "3.x" rather than "3.3", I think. -- Jack Krupansky On Tue, Feb 9, 2016 at 1:50 PM, Jake Luciani wrote: > The Cassandra team is pleased to announce the release of Apache Cassandra > version 3.3. > > *This

Re: Back to the futex()? :(

Thanks for the links, Ben--I'll be sure to give those a read. And yeah, followed the Crowdstrike presentation in detail (including the stuff they called out on Al Tobey's page). Again, the reason for the huge heap is that otherwise my memtable can't actually fit in memory (no off-heap until 3.4),

Re: Scenarios which need Repair

Hi, Can someone take this? ThanksAnuj On Mon, 8 Feb, 2016 at 11:44 pm, Anuj Wadehra wrote: Hi, Setup: We are on 2.0.14. We have some deployments with just one DC(RF:3) while others with two DCs (RF:3,RF:3). We ALWAYS use LOCAL_QUORUM for both Reads

RE: Restart Cassandra automatically

Call me naïve, but we do use an in-house built program for keeping nodes started (based on a flag-check). The program is something that was written for all kinds of daemon processes here, not Cassandra specifically. The basic idea is that is runs a status check. If that fails, and the flag is

Re: ORM layer for cassandra-java?

Look at Achilles and how it models Partition key & clustering columns: https://github.com/doanduyhai/Achilles/wiki/5-minutes-Tutorial#clustered-entities On Tue, Feb 9, 2016 at 12:48 PM, Atul Saroha wrote: > I know the most popular ORM api > >1. Kundera : > >

Re: Scenarios which need Repair

Hi Anuj. I don't think this decision depends on you scenario, but on your write consistency level instead. Maintenance repair is an anti-entropy operation intended to make all nodes consistent. Think of the situation where, with one DC, one of your nodes is down (or being replaced) for a while

ORM layer for cassandra-java?

I know the most popular ORM api 1. Kundera : https://github.com/impetus-opensource/Kundera/wiki/Using-Compound-keys-with-Kundera 2. Hector (outdated- no longer in development) I am bit confuse to model this table into java domain entity structure CREATE TABLE IF NOT EXISTS

Re: Cassandra Collections performance issue

I think the key to your problem might be around "we overwrite every value". You are creating a large number of tombstones, forcing many reads to pull current results. You would do well to rethink why you are having to to overwrite values all the time under the same key. You would be better to

cassandra client testing

Hello, What do people do to test their cassandra client code? Do you a) mock out the cassandra code b) use a framework which simulates cassandra c) actually use cassandra, perhaps inside docker -- Regards Abdul Jabbar Azam twitter: @ajazam

Re: cassandra client testing

I've never seen Scassandra before--neat! For what it's worth, we just use a test keyspace with a lower RF (that is to say, 1). The tables are identical to our prod keyspace, but the permissions are different for the user on our Bamboo instances so that we can test things like table creation etc.

Re: cassandra client testing

http://www.scassandra.org/ From: Abdul Jabbar Azam Reply-To: "user@cassandra.apache.org" Date: Tuesday, February 9, 2016 at 2:23 PM To: "user@cassandra.apache.org" Subject: cassandra client testing Hello, What do people do to test their cassandra client code? Do you a) mock out the

[RELEASE] Apache Cassandra 3.3 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 3.3. *This release contains a critical bug in 3.0 series[4].* If you have installed version >= 3.0 you will need to run 'nodetool upgradesstables -a' on all nodes to receive the fix. Apache Cassandra is a fully

[RELEASE] Apache Cassandra 3.0.3 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 3.0.3. *This release contains a critical bug in 3.0 series[4].* If you have installed version >= 3.0 you will need to run 'nodetool upgradesstables -a' on all nodes to receive the fix. Apache Cassandra is a fully

Re: [RELEASE] Apache Cassandra 3.3 released

Pardon my ignorance, Jake--should we run upgradesstables -a after or before we install 3.3? Thanks! :) ___ Will Hayworth Developer, Engagement Engine Atlassian My pronoun is "they". On Tue, Feb 9, 2016 at 10:50

Re: CASSANDRA-8072

On XX.YY : # service iptables status iptables: Firewall is not running. I put public IP address for listen address on a non-seed node. I still got: INFO 18:14:17 OutboundTcpConnection using coalescing strategy DISABLED ERROR 18:14:48 Exception encountered during startup

stefania.alborghe...@datastax.com

Hi, I am using DSE 4.8.4 Here are the ports Cassandra daemon listens on: tcp0 0 xx.yy:9042 0.0.0.0:* LISTEN 30773/java tcp0 0 127.0.0.1:56498 0.0.0.0:* LISTEN 30773/java tcp0 0 xx.yy:7000 0.0.0.0:*

Re: cassandra client testing

This looks really good. I can see in master that java driver 3.0 support has been added. I can't see out how to generate exceptions. I'd like to test my akka supervisor hierarchy as well. On Tue, 9 Feb 2016 at 22:48 Jeff Jirsa wrote: > http://www.scassandra.org/ > >

Re: [RELEASE] Apache Cassandra 3.3 released

Nice work guys. Just to confirm, if you upgrade from, 2.2.x say, directly to 3.3, you will *not* need to run upgradesstables, right? It seems pretty clear that the answer is no but I just wanted to make sure. Only needed if you got from a 3.x version? Thank you. Sent from my iPhone > On 9

Re: CASSANDRA-8072

Can you make sure you changed the listen address on both hosts, using their respective public IP address and that the seeds and cluster name are the same on both hosts. The seeds should contain the public IP of the seed node. Then verify you can telnet from one host to the other and vice-versa

Re: cassandra client testing

Hello Will, I'll give scassandra a try first, otherwise use a test keyspace. On Tue, 9 Feb 2016 at 22:52 Will Hayworth wrote: > I've never seen Scassandra before--neat! > > For what it's worth, we just use a test keyspace with a lower RF (that is > to say, 1). The

Re: CASSANDRA-8072

Forgot to update this thread. Early afternoon I was able to get 5 node cluster up and running by following the guideline below. Thanks for the help. On Tue, Feb 9, 2016 at 5:09 PM, Stefania Alborghetti < stefania.alborghe...@datastax.com> wrote: > Can you make sure you changed the listen

Re: [RELEASE] Apache Cassandra 3.3 released

Well typically you should run upgradesstables when you upgrade major versions as well https://docs.datastax.com/en/upgrade/doc/upgrade/cassandra/upgradeCassandraDetails.html On Tue, Feb 9, 2016 at 6:11 PM, Will Zhang wrote: > Nice work guys. > > Just to confirm, if

Re: CASSANDRA-8072

One suggestion I have, after recent experience setting up a cluster, is that Cassandra can provide better troubleshooting information to novice such as I. e.g. listen address for seed node (node whose public IP is the same as the address given in seeds) shouldn't be set to localhost. Thanks On

Re: [RELEASE] Apache Cassandra 3.3 released

Adding to Jake's point - it's a noop if you run upgrade sstables and it doesn't need to be upgraded. So just do it and save yourself a headache. On Tue, Feb 9, 2016 at 7:10 PM Jake Luciani wrote: > Well typically you should run upgradesstables when you upgrade major >

Re: best ORM for cassandra

You are probably better off using the driver as you do not need an ORM. Cassandra is not a relational DB. You can find the documentation here  http://docs.datastax.com/en/developer/driver-matrix/doc/common/driverMatrix.html. Pick the version that is applicable to your project. Thanks,Nirmallya

best ORM for cassandra

Hi I am new to cassandra. I am developing an application with cassandra. Which is the best ORM for cassandra? -- Thanks & Regards Raman Gugnani *Senior Software Engineer | CaMS* M: +91 8588892293 | T: 0124-660 | EXT: 14255 ASF Centre A | 2nd Floor | CA-2130 | Udyog Vihar Phase IV |