RE: Commitlogs are filling the Full Disk space and nodes are down

Hi, When you actually say nodetool flush, data from memTable goes to disk based structure as SStables and side by side , commit logs segments for that particular data get written off and its continuous process . May be in your case , you can decrease the value of below uncommented property in

RE: Cassandra nodes are down

Hello, Please check in debug logs for detailed trace, here exact reason can't be figure out. Try your luck there. From: Mokkapati, Bhargav (Nokia - IN/Chennai) [mailto:bhargav.mokkap...@nokia.com] Sent: Monday, January 29, 2018 11:09 PM To: user@cassandra.apache.org Cc: mbhargavna...@gmail

RE: [EXTERNAL] Lot of hints piling up

Check if any warn sign stating “ Node is down” or “Node is coming up” in system.log and also see on that node using nodetool tpstats whether dropped mutations are there or not. From: Jai Bheemsen Rao Dhanwada [mailto:jaibheem...@gmail.com] Sent: Wednesday, October 25, 2017 3:37 AM To: user@c

unsubscribe

Thanks & Regards Amit Singh

Migrating to LCS : Disk Size recommendation clashes

@01D2B47E.E29E7480][cid:image008.jpg@01D2B47E.E29E7480] So are there any restrictions/scenarios due to which 600GB is the preferred one in LCS. Thanks & Regards Amit Singh

RE: Incremental Repair Migration

take hours to be finished if we go ahead with procedure shared by Datastax. So any quick method to reduce that ? Regards Amit Singh From: Jonathan Haddad [mailto:j...@jonhaddad.com] Sent: Tuesday, January 10, 2017 11:50 AM To: user@cassandra.apache.org Subject: Re: Incremental Repair Migration

Incremental Repair Migration

? Thanks & Regards Amit Singh

RE: Incremental repair for the first time

Hi , Generally Upgradesstables are only recommended when you plan to move with Major version like from 2.0 to 2.1 or from 2.1 to 2.2 etc. Since you are doing minor version upgrade no need to run upgradesstables utility. Link by Datastax might be helpful to you : https://support.datastax.com/

RE: Trying to find cause of exception

0.jar:3.3.0] at java.lang.Thread.run(Thread.java:745) [na:1.8.0_111] Caused by: java.lang.NullPointerException: null RICHARD NEY TECHNICAL DIRECTOR, RESEARCH & DEVELOPMENT +1 (978) 848.6640 WORK +1 (916) 846.2353 MOBILE UNITED STATES richard....@aspect.com<mailto:richard@aspect.com> asp

RE: Trying to find cause of exception

Hello, Few pointers : a.) Can you check in system.log for similar msgs like “marking as down” on the node which gives err msg if yes, then please check for GC pause . Heavy load is one of the reason for this. b.)Can you try connecting cqlsh to that node once you get this kind of msg

RE: Handling Leap second delay

Hi , Attached conversation can be of some help to you. Regards Amit Singh From: Sanjeev T [mailto:san...@gmail.com] Sent: Wednesday, December 21, 2016 9:24 AM To: user@cassandra.apache.org Subject: Handling Leap second delay Hi, Can some of you share points on, the versions and handling leap

JConsole Support for SSL in C* 2.0

from this is that only in C* 3.x, we can secure Jconsole over SSL? Also in C* 2.0 , SSL can only be used by clients except nodetool,jconsole ? Please correct me if I am on wrong way . Regards Amit Singh Datastax Certified Developer

RE: C* files getting stuck

Hi All, Please check if anybody has faced below issue and if yes what best can be done to avoid this.? Thanks in advance. Regards Amit Singh From: Amit Singh F [mailto:amit.f.si...@ericsson.com] Sent: Wednesday, June 29, 2016 3:52 PM To: user@cassandra.apache.org<mailto:u

upgradesstables throws error when migrating from 2.0.14 to 2.1.13

Hi All, We are in process of migrating from 2.0.14 to 2.1.13 and we are able to successfully install binaries and make Cassandra 2.1.13 running up and fine. But issue comes up when we try to run nodetool upgradesstables , it gets finished in few seconds only which means it does not find any old

RE: Exclude a host from the repair process

Hi Jean, This option is available in C* version 2.1.x & above, where you can specify hosts in nodetool repair command . For more detail please visit the link below : https://docs.datastax.com/en/cassandra/2.1/cassandra/tools/toolsRepair.html Regards Amit Singh From: Alain RODRI

RE: C* files getting stuck

instance has been our fix so far. I am very interested if anyone else has a solution. I was unable to get a definitive answer from Datastax during the last Cassandra Summit. From: Amit Singh F [mailto:amit.f.si...@ericsson.com] Sent: Thursday, June 30, 2016 7:02 AM To: user@cassandra.apache.org

RE: C* files getting stuck

Hi All, Please check fi anybody has faced below issue and if yes what best can be done to avoid this.? Thanks in advance. Regards Amit Singh From: Amit Singh F [mailto:amit.f.si...@ericsson.com] Sent: Wednesday, June 29, 2016 3:52 PM To: user@cassandra.apache.org Subject: C* files getting

C* files getting stuck

bility that it can occur in higher version too. Regards Amit Singh

RE: *** How to bring up one of the Nodes which is down ***

Hi Lokesh, Please check your Cassandra logs for the downed too and see any exception traces are there or not. From: Carlos Alonso [mailto:i...@mrcalonso.com] Sent: Tuesday, April 12, 2016 3:59 PM To: user@cassandra.apache.org Subject: Re: *** How to bring up one of the Nodes which is down *** H

RE: Lot of GC on two nodes out of 7

. · Concurrent_compactors : Alain righlty pointed out this i.e reduce it to 8. You need to try this. Also please check whether you have mutations drop in other nodes or not. Hope this helps in your cluster too. Regards Amit Singh From: Jonathan Haddad [mailto:j...@jonhaddad.com] Sent: Wednesday, March 02, 2016 9:33 PM

RE: Lot of GC on two nodes out of 7

. · Concurrent_compactors : Alain righlty pointed out this i.e reduce it to 8. You need to try this. Also please check whether you have mutations drop in other nodes or not. Hope this helps in your cluster too. Regards Amit Singh From: Jonathan Haddad [mailto:j...@jonhaddad.com] Sent: Wednesday, March 02, 2016 9:33 PM

RE: Querying on index

Hi Rakesh, Default consistency level of client is set to 1, from your query it seems you are using CQL so could you try same query by setting CONSISTENCY ALL when you enter cqlsh. Regards Amit Singh From: Rakesh Kumar [mailto:dcrunch...@aim.com] Sent: Wednesday, March 02, 2016 3:25 AM To

RE: Gossip Protocol

Hello, To get detailed description/Architecture of Gossip protocol please check the below link : https://wiki.apache.org/cassandra/ArchitectureGossip Also you can try nodetool gossipinfo command , output of this will guide you on details saved by gossip. Regards Amit Singh From: Thouraya TH

Upgrade from 2.0.x to 2.2.x documentation missing

highly appreciated. Thanks in advance Regards Amit Singh

unit test failing when pull is taken

. Regards Amit Singh