Re: Single cluster node restore

You can have situations where rebuilding a node via streaming is painful and slow (generally because there is something bad about the data model like misused secondary indexes or massive partitions). Also, overstreaming can mean you need more disk space to bootstrap a node than you’ll require once

Re: Why does `now()` produce different times within the same query?

Hi, The function is defined here[1]. I hope my email client isn't butchering the code. public static final Function *nowFct *= new NativeScalarFunction("now", TimeUUIDType.*instance*) { public ByteBuffer execute(ProtocolVersion protocolVersion, List parameters) {

Re: Why does `now()` produce different times within the same query?

every now() call in statement is under the hood "replaced" with newly generated uuid. It can happen that they belong to different milliseconds in time. If you need to have same timestamps you need to set them on the client side. @msvaljek 2016-11-29 22:49

Why does `now()` produce different times within the same query?

It appears that a single query that calls Cassandra's `now()` time function may actually cause a query to write or return different times. Is this the expected or defined behavior, and if so, why does it behave like this rather than evaluating `now()` once across an entire statement? This really

Cassandra Upgrade

Hi Everyone, Hypothetically speaking, can I add a new node with version 2.2.8 to a 2.0.14 cluster? Meaning, instead of upgrading the cluster, I'd like to remove a node, clear all its data, install 2.2.8 and add it back to the cluster, with the process eventually performed on all nodes one by one.

Re: Cassandra Upgrade

Hi Shalom. That seems like the long way around doing it. If you clear the data from the node then add it back in then you will have to restream and recompact the data again for each node. Is there a particular reason why you would need to do it this way? The way we do it is to update Cassandra

Re: Cassandra Upgrade

Hi Shalom, There is a pretty good write up of the procedure written up here ( https://docs.datastax.com/en/upgrade/doc/upgrade/cassandra/upgrdCassandraDetails.html). Things to highlight are: - Don't have a repair running while carrying out the upgrade (so that does timebox your upgrade).

Re: Cassandra Upgrade

Thanks Ben and Brooke! @Brooke, I'd like to do that because I want to install Centos 7 on those machines instead of the current Centos 6. To achieve that, I need to make a new installation of the OS, meaning taking the server down. So if that's the case, and I can't perform the upgrade online, why

Re: Which version is stable enough for production environment?

Thanks for all of your responses, it really helps. -- Original -- From: "Harikrishnan Pillai";; Date: Wed, Nov 30, 2016 10:11 AM To: "user"; Subject: Re: Which version is stable enough for production

Re: Which version is stable enough for production environment?

What are the compaction issues / hint corruprions you encountered? Are there JIRA tickets for it? I am curios cause I use 3.10 (trunk) in production. For anyone who is planning to use MVs: They basically work. We use them in production since some months, BUT (it's a quite big one) maintainance is

Re: how to effectively drop table

OK! I'll drop keyspaces. Thanks 2016-11-24 19:14 GMT+08:00 Vladimir Yudovin : > Actually you shouldn't drop tables prior to dropping keyspace. Just drop > keyspace with all its tables. > > Best regards, Vladimir Yudovin, > *Winguzone -

Which version is stable enough for production environment?

Hi Cassandra Experts, We prepare to deploy Cassandra in production env, but we can not confirm which version is stable and recommended, could someone in this mail list give the suggestion? Thanks in advance! Best Regards Discovery 11/30/2016

Re: Which version is stable enough for production environment?

3.0 has "off the heap memtable" impl removed and if you have a requirement for this,its not available.If you don't have the requirement 3.0.9 can be tried out. 3.9 version we did some testing and find lot issues in compaction,hint corruption etc. Regards Hari

RE: Which version is stable enough for production environment?

Some of us want to start as a probe of concept and would like to know --> Why version 3.x is not recommended? From: Long [mailto:on.long...@gmail.com] Sent: 30 November 2016 02:17 To: user@cassandra.apache.org Subject: Re: Which version is stable enough for production environment? You shouldn't

Re: Which version is stable enough for production environment?

Cassandra 2.1.16 From: Discovery Sent: Tuesday, November 29, 2016 5:42 PM To: user Subject: Which version is stable enough for production environment? Hi Cassandra Experts, We prepare to deploy Cassandra in production env, but

Re: Which version is stable enough for production environment?

Why version 3.x is not recommended? Thanks. -- Original -- From: "Harikrishnan Pillai";; Date: Wed, Nov 30, 2016 09:57 AM To: "user"; Subject: Re: Which version is stable enough for production

Re: Which version is stable enough for production environment?

You shouldn't be asking this question as you are preparing to deploy production. Just saying. Original message From: Discovery Date: 2016-11-29 20:59 (GMT-05:00) To: user Subject: Re: Which version is stable enough for production

Re: Cassandra Upgrade

Why would you remove all the data? That doesn't sound like a good idea. Just upgrade the OS and then go through the normal upgrade flow of starting C* with the next version and upgrading sstables. Also, *you will need to go from 2.0.14 -> 2.1.16 -> 2.2.8* and upgrade sstables at each stage of the

Re: Cassandra Upgrade

Thanks for the info Kurt, I guess I'd go with the normal upgrade procedure then. Thanks again for the help everyone. Shalom Sagges DBA T: +972-74-700-4035 We Create Meaningful

Java Collections.emptyList inserted as null object in cassandra

Filed Type in cassandra : List I am trying to insert Collections.emptyList() from spark to cassandra list field. In cassandra it stores as null object. How can i avoid null values here. -- Selvam Raman "லஞ்சம் தவிர்த்து நெஞ்சம் நிமிர்த்து"

Re: Java Collections.emptyList inserted as null object in cassandra

It is not possible. Internally Cassandra flattens your data out into a set of key-value-pairs. All collection types, including lists, are nothing more than a thin layer of schema over a clustered set of key-value-pairs, so on disk there is no difference between an empty list and a list that

Re: Java Collections.emptyList inserted as null object in cassandra

It is not possible. Internally Cassandra flattens your data out into a set of key-value-pairs. All collection types, including lists, are nothing more than a thin layer of schema over a clustered set of key-value-pairs, so on disk there is no difference between an empty list and a list that

Re: Which version is stable enough for production environment?

Hi Brooke, Just had a quick look on your code and I will promise that your LTS version will have the same issues with MVs as any other version. For details check CASSANDRA-12905 or CASSANDRA-12888. 2016-11-30 8:35 GMT+01:00 Brooke Jensen : > 2.1 will be end of life soon.

Re: Which version is stable enough for production environment?

2.1 will be end of life soon. We have a number of customers running 3.7 in production and it's quite stable. However you should always test in a lower environment first with your data model to be sure. If you're interested, we have made available a patched version of 3.7

Single cluster node restore

Hi. I have a question about Cassandra backup-restore strategies. As far as I understand Cassandra has been designed to survive hardware failures by relying on data replication. It seems like people still want backup/restore for case when somebody accidentally deletes data or the data gets