Re: repair_history maintenance

That sounds good to me. Unless there are objections I'll start doing that on a scheduled bases. Cheers On Fri, Sep 23, 2016 at 11:55 AM Chris Lohfink wrote: > Probably should just periodically truncate/clear snapshots when gets too > big (will probably take months before

Re: repair_history maintenance

Probably should just periodically truncate/clear snapshots when gets too big (will probably take months before noticeable). I opened https://issues.apache.org/jira/browse/CASSANDRA-12701 for discussion on if it should use TTLs Chris On Thu, Sep 22, 2016 at 1:28 PM, sfesc...@gmail.com

Re: Lightweight tx is good enough to handle counter?

This might help you: https://github.com/edwardcapriolo/ec/blob/master/src/test/java/Base/CompareAndSwapTest.java It counts using lwt's with multiple threads. On Fri, Sep 23, 2016 at 2:31 PM, Jaydeep Chovatia < chovatia.jayd...@gmail.com> wrote: > Since SERIAL consistency is not supported for

Re: Lightweight tx is good enough to handle counter?

Since SERIAL consistency is not supported for batch updates, I used QUORUM for the operation. On Fri, Sep 23, 2016 at 11:23 AM, DuyHai Doan wrote: > What is the consistency level used for the batch query ? > > > On Fri, Sep 23, 2016 at 8:19 PM, Jaydeep Chovatia < >

Re: Lightweight tx is good enough to handle counter?

What is the consistency level used for the batch query ? On Fri, Sep 23, 2016 at 8:19 PM, Jaydeep Chovatia < chovatia.jayd...@gmail.com> wrote: > Ok. But I am trying to understand a scenario under which this mis-match > can occur with light-weight tx. > > On Fri, Sep 23, 2016 at 11:14 AM,

Re: Lightweight tx is good enough to handle counter?

Ok. But I am trying to understand a scenario under which this mis-match can occur with light-weight tx. On Fri, Sep 23, 2016 at 11:14 AM, DuyHai Doan wrote: > Lightweight transaction is not available for counters, for the simple > reason that counters are not idempotent >

Re: Lightweight tx is good enough to handle counter?

Lightweight transaction is not available for counters, for the simple reason that counters are not idempotent On Fri, Sep 23, 2016 at 8:10 PM, Jaydeep Chovatia < chovatia.jayd...@gmail.com> wrote: > We have a following table: > > create table mytable { > > id int, > count int static, > rec_id

Lightweight tx is good enough to handle counter?

We have a following table: create table mytable { id int, count int static, rec_id int, primary key (id, rec_id) }; The count in the table represents how many records (rec_id clustering columns) exists. So when we add new a new record we do it following way: UNLOGGED BATCH insert into mytable

Re: Upgrading from Cassandra 2.1.12 to 3.0.9

To me clear about the mixed versions. You do not want to do it. Especially if the versions are very far apart. Typically you can not run repair in mixed versions. You can not do schema changes with mixed versions. Data files from new versions are not readable from old versions. Basically you

Re: Upgrading from Cassandra 2.1.12 to 3.0.9

Oh yeah, and to the second question, can you run a cluster with mixed versions, the answer is absolutely not in any sort of sane way. On Fri, Sep 23, 2016 at 10:01 AM SmartCat - Scott Hirleman < sc...@smartcat.io> wrote: > I think the TLP team are recommending the approach I would as well, which

Re: Upgrading from Cassandra 2.1.12 to 3.0.9

I think the TLP team are recommending the approach I would as well, which is to spin up a new cluster and copy your data into it for testing purposes. If your app isn't in production yet, playing around with 3.7 is great, really helps the community as Jon said; the word "upgrading" will set off

Re: Upgrading from Cassandra 2.1.12 to 3.0.9

Thank you Joaquim for the advice. I seem to have sent this email with the wrong subject. It should have been Upgrading from Cassandra 2.1.12 to 3.7, but too late now. The plan is to upgrade from 2.1.12 to 3.7 and to maintain a heterogeneous cluster only for a short time, while we observe how

Re: Upgrading from Cassandra 2.1.12 to 3.0.9

I strongly recommend not upgrading to 3.7. Here's my thoughts on Tick Tock releases, copy / pasted from a previous email I wrote on this ML: 3.7 falls under the Tick Tock release cycle, which is almost completely untested in production by experienced operators. In the cases where it has been

Re: Upgrading from Cassandra 2.1.12 to 3.0.9

Hello Razi, Since you were using a highly stable version of 2.1.x, you may want to stick with using 3.0.9. 3.7 has introduced many great features, but has not been as heavily tested in production as 3.0.9. Running heterogenous clusters, even when using the same major version (e.g. 3.0.8 and

Re: Nodetool rebuild exception on c*-2.0.17

Hi, >From "nodetool status" output, it looks like the cluster is running ok. The exception itself simply says that data streaming fails during nodetool rebuild. This could be due to possible network hiccup. It is hard to say. You need to do further investigation. For example, you can run

Re: How to query '%' character using LIKE operator in Cassandra 3.7?

Hi, Jim, What pattern should be used to search “ends with ‘%escape’ “ with your conception? Thanks, Mikhail > On 22 Sep 2016, at 18:51, Jim Ancona wrote: > > To answer DuyHai's question without introducing new syntax, I'd suggest: >> LIKE '%%%escape' means STARTS WITH

Upgrading from Cassandra 2.1.12 to 3.0.9

Hello all, I would like to upgrade my Cassandra cluster from 2.1.12 to 3.7. I have read the following documentation: · http://docs.datastax.com/en/latest-upgrade/upgrade/cassandra/upgrdCassandra.html · https://github.com/apache/cassandra/blob/cassandra-3.7/NEWS.txt but still

Re: Nodetool repair

OK. If you still have issues after setting streaming_socket_timeout_in_ms != 0, consider increasing request_timeout_in_ms to a high value, say 1 or 2 minutes. See comments in https://issues.apache.org/jira/browse/CASSANDRA-7904Regarding 2.1, be sure to test incremental repair on your data

Re: Help on temporal data modeling

yes it would. Whether next_billing_date is timestamp or date wouldn't make any difference on scanning all partitions. If you want to them to be on the same node, you can use composite key, but there's a trade off. The nodes may get unbalanced, so you have to do the math to figure out if your

Re: Help on temporal data modeling

Thanks, for you answer. Wouldn’t simple `select * from subscriptions where next_billing_date = '2016-10-25’` require full scan of all partitions? > On 23 Sep 2016, at 14:28, Peter Lin wrote: > > > Ignoring noSql for a minute, the standard way of modeling this in car and >

Re: understanding partitions

Hi, One more thing to consider is wide partition. Even though theoretically Cassandra supports wide rows, practical limit is max 100 MB per partition. So based on your use-case and model, you may have to split the data into partitions so that wide partitions are not created. Regards, Firdousi

Re: Help on temporal data modeling

Ignoring noSql for a minute, the standard way of modeling this in car and health insurance is with effective/expiration day. Commonly called bi-temporal data modeling. How people model bi-temporal models varies quite a bit from first hand experience, but the common thing is to have transaction

#RE: During writing data into Cassandra 3.7.0 using Python driver 3.7 sometime loose Connection because of Server NullPointerException (Help please!)

Hi Sam, Thank you for the prompt reply! We will raise a ticket with Cassandra Jira. In between I am posting here the Exception from the client too. The client is Python script running Python 2.7.12. = Traceback (most recent call last): File "vssandra_v5.py", line 132,

Re: Help on temporal data modeling

Hi Denis, You might want to have a look at - Materialized views http://www.datastax.com/dev/blog/new-in-cassandra-3-0-materialized-views - Secondary index https://docs.datastax.com/en/cql/3.3/cql/cql_using/useWhenIndex.html My 2 cents: make sure to understand the implications before moving

Re: data file directory path customization

Hi Alain, Thank you for your feedback, the problem was the space character before the data_files_directories parameter. As you said the the YAML is very case sensitive. Many thanks for your feedback and have a nice day. Regards --- Mehdi Bada | Consultant Phone: +41 32 422 96 00 |

RE: data file directory path customization

Hi Mehdi, Did you set it same for all nodes in the cluster? Please check the space between the key and value and also before the key. Key (data_files_directories, commitlog_directory, saved_caches_directory). Check the write permission of the parent directory too. Hope this helps! Kind

Re: data file directory path customization

Hi Mehdi, > After configuring this 3 variables (parameters) in the cassandra-yaml, I > had the following issues > With the new apache cassandra 3.7 version, It is possible to setup a > customizable path for data_files, saved_caches and commit_log in the > configuration file (cassandra.yaml)? >

Re: During writing data into Cassandra 3.7.0 using Python driver 3.7 sometime loose Connection because of Server NullPointerException (Help please!)

The stacktrace suggests that when a connection is being established, either the can_login or is_superuser attribute of the authenticated role is null, which is definitely a bug as there should be no way to create a role in that state. Could you please open a ticket on

During writing data into Cassandra 3.7.0 using Python driver 3.7 sometime loose Connection because of Server NullPointerException (Help please!)

Hi, In one of our C* cluster we are using the latest Cassandra 3.7.0 (datastax-ddc.3.70) with Python driver 3.7. We are trying to insert 2 million row or more data into the database, it works but sometimes we are getting "Null pointer Exception". I am quoting the Exception here. Any help

Help on temporal data modeling

Hi! I have question regarding data modelling. Let’s say that I have `subscriptions` table with two columns `subscription_id text` and `next_billing_date timestamp`. How do I model a table to efficiently query all subscriptions due today (something like `where next_billing_date <= today`)

data file directory path customization

Hi all, With the new apache cassandra 3.7 version, It is possible to setup a customizable path for data_files, saved_caches and commit_log in the configuration file (cassandra.yaml)? I ask the question because during some test, I wanted to setup the path for : - data_files_directories -