Re: nodetool repair failure

What version of Cassandra? -- Michael On 06/26/2017 09:53 PM, Balaji Venkatesan wrote: > Hi All, > > When I run nodetool repair on a keyspace I constantly get "Some repair > failed" error, there are no sufficient info to debug more. Any help? > > Here is the stacktrace > >

nodetool repair failure

Hi All, When I run nodetool repair on a keyspace I constantly get "Some repair failed" error, there are no sufficient info to debug more. Any help? Here is the stacktrace == [2017-06-27 02:44:34,275] Some repair failed

Re: Cassandra with dcos

While someone here might know the answer, I think you'll want to ask on the DC/OS mailing list for best chance of getting a response. The Apache Cassandra Project doesn't maintain the code you're asking about. The DC/OS mailing list here: https://groups.google.com/a/dcos.io/forum/#!forum/users

Cassandra with dcos

Hi guys, Having tested adding a new datacenter with existing data, I realized that there is no rebuild command available in dcos-cassandra-service. So the question is : how do we sync a new added datacenter with existing ones (I mean having existing data) ? I tried on dcos ML but didn’t have

Re: Linux version update on DSE

Right, we are just upgrading Linux on AWS. C* will remain at same version. > On Jun 26, 2017, at 6:05 PM, Hannu Kröger wrote: > > I understood he is updating linux, not C* > > Hannu > On 27 June 2017 at 02:04:34, Jonathan Haddad (j...@jonhaddad.com >

[RELEASE] Apache Cassandra 2.2.10 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 2.2.10. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source

[RELEASE] Apache Cassandra 2.1.18 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 2.1.18. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source

Re: Linux version update on DSE

I understood he is updating linux, not C* Hannu On 27 June 2017 at 02:04:34, Jonathan Haddad (j...@jonhaddad.com) wrote: It sounds like you're suggesting adding new nodes in to replace existing ones. You can't do that because it requires streaming between versions, which isn't supported. You

Re: Linux version update on DSE

Oops, I read that wrong, sorry. You want to upgrade the OS. Disregard my email. On Mon, Jun 26, 2017 at 4:04 PM Jonathan Haddad wrote: > It sounds like you're suggesting adding new nodes in to replace existing > ones. You can't do that because it requires streaming

Re: Linux version update on DSE

It sounds like you're suggesting adding new nodes in to replace existing ones. You can't do that because it requires streaming between versions, which isn't supported. You need to take a node down, upgrade the C* version, then start it back up. Jon On Mon, Jun 26, 2017 at 3:56 PM Nitan Kainth

Re: Linux version update on DSE

It's vnodes. We will add to replace new ip in yaml as well. Thank you. Sent from my iPhone > On Jun 26, 2017, at 4:47 PM, Hannu Kröger wrote: > > Looks Ok. Step 1.5 would be to stop cassandra on existing node but apart from > that looks fine. Assuming you are using same

Re: Incorrect quorum count in driver error logs

Yes. On Mon, Jun 26, 2017 at 5:45 PM Hannu Kröger wrote: > Just to be sure: you have only one datacenter configured in Cassandra? > > Hannu > > On 27 Jun 2017, at 0.02, Rutvij Bhatt wrote: > > Hi guys, > > I observed some odd behaviour with our Cassandra

Re: Linux version update on DSE

Looks Ok. Step 1.5 would be to stop cassandra on existing node but apart from that looks fine. Assuming you are using same configs and if you have hard coded the token(s), you use the same. Hannu > On 26 Jun 2017, at 23.24, Nitan Kainth wrote: > > Hi, > > We are

Re: Incorrect quorum count in driver error logs

Just to be sure: you have only one datacenter configured in Cassandra? Hannu > On 27 Jun 2017, at 0.02, Rutvij Bhatt wrote: > > Hi guys, > > I observed some odd behaviour with our Cassandra cluster the other day while > doing some maintenance operation and was wondering if

Incorrect quorum count in driver error logs

Hi guys, I observed some odd behaviour with our Cassandra cluster the other day while doing some maintenance operation and was wondering if anyone would be able to provide some insight. Initially, I started a node up to join the cluster. That node appeared to be having issues joining due to some

Linux version update on DSE

Hi, We are planning to update linux for C* nodes version 3.0. Anybody has steps who did it recent past. Here are draft steps, we are thinking: 1. Create new node. It might have a different IP address. 2. Detach mounts from existing node 3. Attach mounts to new Node 4. Start C*

Re: Stable cassandra version with frozen UDTs

So according to what Michael wrote 3.11.x will be stable branch now. You can stick to it or revert to 3.0.x (latest is 3.0.14), if you don't need 3.x features. Best regards, Vladimir Yudovin, Winguzone - Cloud Cassandra Hosting On Mon, 26 Jun 2017 13:51:32 -0400 Ali Akhtar

Re: Timeout while trying to acquire available connection

How many client connections are hitting your cluster? Have you looked at tuning connection pool? https://github.com/datastax/java-driver/tree/3.x/manual/pooling -- Jacob Shadix On Mon, Jun 26, 2017 at 2:50 PM, Ivan Iliev wrote: > Hello everyone! > > I am seeing

Timeout while trying to acquire available connection

Hello everyone! I am seeing recent behavior of apps being not able to communicate to the Cassandra cluster with the following errors: All host(s) tried for query failed (tried: cassandra2-test:9042 (com.datastax.driver.core.exceptions.DriverException: Timeout while trying to acquire available

Re: Stable cassandra version with frozen UDTs

So, which cassandra version is the most stable / production ready currently? I'm fine with reverting to 2.x if needed. On Mon, Jun 26, 2017 at 8:37 PM, Michael Shuler wrote: > On 06/26/2017 10:17 AM, Vladimir Yudovin wrote: > > > > In terms of tick-tock releases odd

Re: Stable cassandra version with frozen UDTs

On 06/26/2017 10:17 AM, Vladimir Yudovin wrote: > > In terms of tick-tock releases odd releases (e.g. 3.11) are bug fixes. The last tick-tock feature release was 3.10. Tick-tock releases are no more. The project has moved back to development on stable release series. The bug-fixes on top of the

Re: Stable cassandra version with frozen UDTs

Is that version going to be stable for production? Well, 1M$ question )). There is a lot of discussion on this topic. In terms of tick-tock releases odd releases (e.g. 3.11) are bug fixes. But I guess latest 3.0.x (3.0.14 now) should more stable. Best regards, Vladimir Yudovin, Winguzone

Re: Question about materialized view

This is handled by updateAffectsView in org.apache.cassandra.db.view.View. It will scan over each row to be updated in the base table and see that the column is not included in the view definition and skip the update. -- Michael Mior mm...@apache.org 2017-06-21 2:41 GMT-04:00 web master

Re: Question: Behavior of inserting a list multiple times with same timestamp

Hi, INSERT INTO test.test (k , v ) VALUES ( 1 ,[10]) USING TIMESTAMP 1000; INSERT INTO test.test (k , v ) VALUES ( 1 ,[20]) USING TIMESTAMP 1000; INSERT INTO test.test (k , v ) VALUES ( 1 ,[30]) USING TIMESTAMP 1000; SELECT * FROM test.test ; cqlsh SELECT * FROM test.test ; k | v

Re: Stable cassandra version with frozen UDTs

Is that version going to be stable for production? I'm looking for something that I can just install, add nodes when needed, but otherwise not have to worry or think about, even if it means downgrading to a lower version and rewriting some of the code involving UDTs. On Mon, Jun 26, 2017 at 3:51

Re: Stable cassandra version with frozen UDTs

Latest comment in this JIRA is "I've committed to 3.11". 3.11 change log also contains "* Fix validation of non-frozen UDT cells (CASSANDRA-12916)" (merged from 3.10) So try version 3.11 Best regards, Vladimir Yudovin, Winguzone - Cloud Cassandra Hosting On Thu, 22 Jun 2017

Re: Secondary Index

The second query will be much more efficient as the partition key restriction is applied before the one using the indexed column. Only the replicas for that partition will be involved in query 2, whereas query 1 will be distributed to enough replicas to cover the whole token ring. Also (& this