AW: The changing clustering key

Hi, your primary goal is to fetch a user by dept_id and user_id and additionally keep versions of the user data? {    dept_id text,    user_id text,    mod_date timestamp,    user_name text,    PRIMARY KEY ((dept_id,user_id), mod_date) WITH CLUSTERING ORDER BY (mod_date DESC); } There is a

Re: Why are automatic anti-entropy repairs required when hinted hand-off is enabled?

I had asked a similar/related question - on how to carry out repair, etc and got some useful pointers. I would highly recommend the youtube video or the slideshare link below (both are for the same presentation). https://www.youtube.com/watch?v=1Sz_K8UID6E

Re: The changing clustering key

thanks for the pointer. Let me readup more on Materialized views and see if that helps solve our problem. I do know that its not supported in our current version 2.2.x but I can explore moving to Cassandra 3. On Fri, 7 Apr 2017 at 04:22 Eric Stevens wrote: > Just curious if

Re: Unsubscribe

Hi John, Please send an email to user-unsubscr...@cassandra.apache.org to unsubscribe from this list. On Fri, Apr 7, 2017 at 8:58 AM, John Buczkowski wrote: > *From:* eugene miretsky [mailto:eugene.miret...@gmail.com] > *Sent:* Thursday, April 06, 2017 4:36 PM > *To:*

Re: Copy from CSV on OS X problem with varint values <= -2^63

Stefania Downloading and simply running from folder without homebrew interference it now looks like the driver matches what you say in the last email. I will try writing variants again to confirm it works. cqlsh --debug Using CQL driver: Using connect timeout: 5 seconds Using 'utf-8' encoding

How does clustering key works with TimeWindowCompactionStrategy (TWCS)

Hi guys, I'm a new and happy user of Cassandra. We are using Cassandra for time series data so we choose TWCS because of its predictability and its ease of configuration. My question is we have a table with the following schema: CREATE TABLE IF NOT EXISTS customer_view ( customer_id bigint,

Unsubscribe

From: eugene miretsky [mailto:eugene.miret...@gmail.com] Sent: Thursday, April 06, 2017 4:36 PM To: user@cassandra.apache.org Subject: Why are automatic anti-entropy repairs required when hinted hand-off is enabled? Hi, As I see it, if hinted handoff is enabled, the only time data can

Why are automatic anti-entropy repairs required when hinted hand-off is enabled?

Hi, As I see it, if hinted handoff is enabled, the only time data can be inconsistent is when: 1. A node is down for longer than the max_hint_window 2. The coordinator node crushes before all the hints have been replayed Why is it still recommended to perform frequent automatic repairs,

Re: The changing clustering key

Just curious if you've looked at materialized views. Something like: CREATE MATERIALIZED VIEW users_by_mod_date AS SELECT dept_id,mod_date,user_id,user_name FROM users WHERE mod_date IS NOT NULL PRIMARY KEY (dept_id,mod_date,user_id) WITH CLUSTERING ORDER BY (mod_date

Re: Node always dieing

i3 are having those issues more than the other instances it seems. Not the first report I heard about. Regards, Carlos Juzarte Rolo Cassandra Consultant / Datastax Certified Architect / Cassandra MVP Pythian - Love your data rolo@pythian | Twitter: @cjrolo | Skype: cjr2k3 | Linkedin:

Re: Node always dieing

Yes but this time I going to give lots of time between killing and pickup. Thanks a lot. On 04/06/2017 05:31 PM, Avi Kivity wrote: > > Your disk is bad. Kill that instance and hope someone else gets it. > > > On 04/06/2017 07:27 PM, Cogumelos Maravilha wrote: >> >> Interesting >> >> [

Re: Node always dieing

Your disk is bad. Kill that instance and hope someone else gets it. On 04/06/2017 07:27 PM, Cogumelos Maravilha wrote: Interesting [ 720.693768] blk_update_request: I/O error, dev nvme0n1, sector 1397303056 [ 750.698840] blk_update_request: I/O error, dev nvme0n1, sector 1397303080 [

Re: Node always dieing

Interesting [ 720.693768] blk_update_request: I/O error, dev nvme0n1, sector 1397303056 [ 750.698840] blk_update_request: I/O error, dev nvme0n1, sector 1397303080 [ 1416.202103] blk_update_request: I/O error, dev nvme0n1, sector 1397303080 On 04/06/2017 05:26 PM, Avi Kivity wrote: > > Is

Re: Node always dieing

Is there anything in dmesg? On 04/06/2017 07:25 PM, Cogumelos Maravilha wrote: Now dies and restart (systemd) without logging why system.log INFO [Native-Transport-Requests-2] 2017-04-06 16:06:55,362 AuthCache.java:172 - (Re)initializing RolesCache (validity period /update interval/max

Re: Node always dieing

Now dies and restart (systemd) without logging why system.log INFO [Native-Transport-Requests-2] 2017-04-06 16:06:55,362 AuthCache.java:172 - (Re)initializing RolesCache (validity period /update interval/max entries) (2000/2000/1000) INFO [main] 2017-04-06 16:17:42,535

Re: Node Gossiping Information.

I am using cassandra 2.1, is it possible to manually make a node to gossip with a particular set of nodes or update gossip info to current to a particular node. I don't think it's possible just checking if that can be done. As i have mentioned i occasionally see hinted handoff threads getting

Re: Node always dieing

find /mnt/cassandra/ \! -user cassandra nothing I've found some "strange" solutions on Internet chmod -R 2777 /tmp chmod -R 2775 cassandra folder Lets give some time to see the result On 04/06/2017 03:14 PM, Michael Shuler wrote: > All it takes is one frustrated `sudo cassandra` run. Checking

Re: Node always dieing

All it takes is one frustrated `sudo cassandra` run. Checking only the top level directory ownership is insufficient, since root could own files/dirs created below the top level. Find all files not owned by user cassandra: `find /mnt/cassandra/ \! -user cassandra` Just another thought. --

Re: Node always dieing

We tested in c4 instances but EBS is too slow. So we deployed for production in i3. It was running with 5 nodes without problems but we started running out of space so we added another node. And is this last node that is giving problems. I've already terminated the instance and created another

Re: Node always dieing

There was some issue with the i3 instances and Cassandra. Did you had this cluster running always on i3? On Apr 6, 2017 13:06, "Cogumelos Maravilha" wrote: > Limit Soft Limit Hard Limit > Units > Max cpu time unlimited

Re: Node always dieing

Limit Soft Limit Hard Limit Units Max cpu time unlimitedunlimited seconds Max file size unlimitedunlimited bytes Max data size unlimitedunlimited

The changing clustering key

Dear Cassandra experts, I have a data modeling question for cases where data needs to be sorted by keys which can be modified. So , say we have a user table { dept_id text, user_id text, user_name text, mod_date timestamp PRIMARY KEY (dept_id,user_id) } Now I can query cassandra to

Re: Node always dieing

Limits: You should check them in /proc/$pid/limits 2017-04-06 12:48 GMT+02:00 Cogumelos Maravilha : > Yes C* is running as cassandra: > > cassand+ 2267 1 99 10:18 ?00:02:56 java > -Xloggc:/var/log/cassandra/gc.log -ea -XX:+UseThreadPriorities >

Re: Node always dieing

Yes C* is running as cassandra: cassand+ 2267 1 99 10:18 ?00:02:56 java -Xloggc:/var/log/cassandra/gc.log -ea -XX:+UseThreadPriorities -XX:Threa... INFO [main] 2017-04-06 10:35:42,956 Config.java:474 - Node configuration:[allocate_tokens_for_keyspace=null;

Re: Node always dieing

Have you checked the effective limits of a running CS process? Is CS run as Cassandra? Just to rule out missing file perms. Am 06.04.2017 12:24 schrieb "Cogumelos Maravilha" < cogumelosmaravi...@sapo.pt>: >From cassandra.yaml: hints_directory: /mnt/cassandra/hints data_file_directories: -

Re: Node always dieing

From cassandra.yaml: hints_directory: /mnt/cassandra/hints data_file_directories: - /mnt/cassandra/data commitlog_directory: /mnt/cassandra/commitlog saved_caches_directory: /mnt/cassandra/saved_caches drwxr-xr-x 3 cassandra cassandra 23 Apr 5 16:03 mnt/ drwxr-xr-x 6 cassandra

Re: Node always dieing

Cassandra cannot write an SSTable to disk. Are you sure the disk/volume where SSTables reside (normally /var/lib/cassandra/data) is writeable for the CS user and has enough free space? The CDC warning also implies that. The other warnings indicate you are probably not running CS as root and you

Node always dieing

Hi list, I'm using C* 3.10 in a 6 nodes cluster RF=2. All instances type i3.xlarge (AWS) with 32GB, 2 cores and SSD LVM XFS formated 885G. I have one node that is always dieing and I don't understand why. Can anyone give me some hints please. All nodes using the same configuration. Thanks in