Re: Removed node is not completely removed

Thanks Sebastian, a restart solved the problem! On Wed, Oct 14, 2015 at 3:46 PM, Sebastian Estevez < sebastian.este...@datastax.com> wrote: > We still keep endpoints in memory. Not sure how you git to this state but > try a rolling restart. > On Oct 14, 2015 9:43 AM, "Tom van den Berge"

Re: Accessing dynamic columns via cqlsh

Thank you Eric, I think we have a limited number of dynamically named columns but I'm not inclined to have them added in the schema. I have just managed to do what I want with the schema below. But It cost me my secondary index on eventId. Because eventId is a clustering_key it's not yet

Re: unchecked_tombstone_compaction - query

Hello Deepak, The dev@cassandra list is exclusive for development announcements and discussions, so I will reply to users@cassandra as someone else might have a similar question. Basically, there is pre-check, that defines which sstables are eligible for single-sstable tombstone compaction, and

RE: Accessing dynamic columns via cqlsh

I do not think that cqlsh provides a way to get internal data. I hope I am wrong... -Original Message- From: Onur Yalazı [mailto:onur.yal...@8digits.com] Sent: Thursday, October 15, 2015 10:54 AM To: user@cassandra.apache.org Subject: Accessing dynamic columns via cqlsh Hello, I have a

Re: Accessing dynamic columns via cqlsh

If the columns are not dynamically named (as in "actionId" and "code") you should be able to add that to your CQL table definition with ALTER TABLE, and those columns should be available in the query results. If the columns *are* dynamically named, and you can't reasonably add every option to the

Re: LOCAL_SERIAL

You probably could, but if I were you, I'd consider a tool built for that purpose, such as Zookeeper. It'd open up access to a lot of other great cluster coordination features. On Thu, Oct 15, 2015 at 8:47 AM Jan Algermissen wrote: > Hi, > > suppose I have two data

Re: LOCAL_SERIAL

ZK seems a little overkill for just 1 feature though. LOCAL_SERIAL is fine if all you want to do is keep a handful of keys up to date. There’s a massive cost in adding something new to your infrastructure, and imo, very little gain in this case. > On Oct 15, 2015, at 8:29 AM, Eric Stevens

LOCAL_SERIAL

Hi, suppose I have two data centers and want to coordinate a bunch of services in each data center (for example to load data into a per-DC system that is not DC-aware (Solr)). Does it make sense to use CAS functionality with explicit LOCAL_SERIAL to 'elect' a leader per data center to do the

Accessing dynamic columns via cqlsh

Hello, I have a cassandra cluster from pre-cql era and I am having problems accessing data via cqlsh. As you can see below, I can not reach dynamic columns via cqlsh but they are accessible via cassandra-cli. How can I make the data shown on cqlsh? cqlsh:automation> select * from

Re: Re : Replication factor for system_auth keyspace

On Thu, Oct 15, 2015 at 10:24 AM, sai krishnam raju potturi < pskraj...@gmail.com> wrote: > we are deploying a new cluster with 2 datacenters, 48 nodes in each DC. > For the system_auth keyspace, what should be the ideal replication_factor > set? > > We tried setting the replication factor

Cassandra 2.2.1 stuck at 100% on Windows

Hi, We are running Cassandra 2.2.1 on Windows 2008R2, and we see that multiple Nodes are stuck at 100% CPU bringing the whole VM to a halt. We suspect that there is another process that IT/Windows is causing the CPU issue, but the problem is Cassandra does NOT recover, the CPU utilization start

Re: Cassandra 2.2.1 stuck at 100% on Windows

On Thu, Oct 15, 2015 at 6:04 PM, Alaa Zubaidi (PDF) wrote: > We are running Cassandra 2.2.1 on Windows 2008R2, and we see that multiple > Nodes are stuck at 99% CPU bringing the whole VM to a halt. > We suspect that there is another process that IT/Windows is causing the >

Cassandra 2.2.1 stuck at 100% on Windows

Hi, We are running Cassandra 2.2.1 on Windows 2008R2, and we see that multiple Nodes are stuck at 99% CPU bringing the whole VM to a halt. We suspect that there is another process that IT/Windows is causing the CPU issue, but the problem is Cassandra does NOT recover, the CPU utilization start

Re: unchecked_tombstone_compaction - query

On Thu, Oct 15, 2015 at 9:01 AM, Paulo Motta wrote: > (OP says:) So - isn't setting unchecked_tombstone_compaction to "true" a >> dangerous setting? Won't it cause resurrections? What is the use case for >> this knob, and when do I know I can set it to true safely? >>

Re: Collections (MAP) data in Column Family

On Wed, Oct 14, 2015 at 10:03 PM, Saladi Naidu wrote: > Thanks for the reply. yes this indeed due to range tombstones with MAP > data, even after tombstone past the gc_grace_poeriod and compactions ran in > cluster, still no change with tombstone data in SSTables. Do you

Re : Replication factor for system_auth keyspace

hi; we are deploying a new cluster with 2 datacenters, 48 nodes in each DC. For the system_auth keyspace, what should be the ideal replication_factor set? We tried setting the replication factor equal to the number of nodes in a datacenter, and the repair for the system_auth keyspace took

RE: reiserfs - DirectoryNotEmptyException

It is deployed on an existing cluster but will be migrated soon to a different file system & Linux distribution. -Original Message- From: Michael Shuler [mailto:mshu...@pbandjelly.org] On Behalf Of Michael Shuler Sent: Wednesday, October 14, 2015 6:02 PM To: user@cassandra.apache.org