Tables showing up as our_table-147a2090ed4211e480153bc81e542ebd/ in data dir

Using 2.1.4, tables in our data/ directory are showing up as our_table-147a2090ed4211e480153bc81e542ebd/ instead of as our_table/ Why would that happen? We're also seeing lagging compactions and high cpu usage. Thanks, Don

Re: Best Practice to add a node in a Cluster

Interesting Eric !!! Not sure if this would be allowed. Alter keyspace to RF=3 and then add a node. On Tue, Apr 28, 2015 at 8:54 PM, Eric Stevens wrote: > I would double check in a test cluster (or with a tool like CCM to confirm > to set up a local throwaway cluster), but for this *specific* us

Re: How to use nodetool ring only for one data center

When we have multi datacenter . In output datacenter like DC1 etc is not easy to associate with each node like we have RAC . On 28 April 2015 at 16:30, Rahul Neelakantan wrote: > Do you want this for some sort of reporting requirement? If so you may be > able to write a quick she'll script using

Re: How to use nodetool ring only for one data center

Do you want this for some sort of reporting requirement? If so you may be able to write a quick she'll script using grep to remove the unwanted data Rahul > On Apr 28, 2015, at 7:24 PM, Surbhi Gupta wrote: > > Hi, > > I wanted to know, how can we get the information of the token rings only fo

How to use nodetool ring only for one data center

Hi, I wanted to know, how can we get the information of the token rings only for one data centers when using vnodes and multiple data center. Thanks Surbhi

Denormalization leads to terrible, rather than better, Cassandra performance -- I am really puzzled

Cassandra gurus, I am really puzzled by my observations,and hope to get some help explaining the results. Thanks in advance. I think it has always been advocated in Cassandracommunity that de-normalization leads to better performance. I wanted to seehow much performance improvement it can offer, bu

Re: New node got stuck joining the cluster after a while

Thanks very much for answering! Do you think that after failing the joining task of a node to the cluster should I run some repairs and cleanups? Thanks! On Tue, Apr 28, 2015 at 5:13 AM, Carlos Rolo wrote: > Hi, > > The 2.1.x series is not recommeded for use, especially the first versions. > I

Re: Best Practice to add a node in a Cluster

I would double check in a test cluster (or with a tool like CCM to confirm to set up a local throwaway cluster), but for this *specific* use case (going from RF==NodeCount to RF==NodeCount with a higher number) you should be able to have a simpler path. Set RF=3 before you add your new node, then

RE: minimum bandwidth requirement between two Geo Redundant sites of Cassandra database

We will be anxious to confirm results in production but we have been seeing 30 ms or less as best; at 45 ms we start having more than tolerable errors, at 50 ms we start to disregard the usability. We are also looking into features from Oracle DATA Guard such as ‘Apply Lag’ and ‘Transport Lag’

Re: New node got stuck joining the cluster after a while

Hi, The 2.1.x series is not recommeded for use, especially the first versions. I would downgrade to 2.0.14 or if must stay on 2.1 upgrade your cluster to 2.1.4 or the imminent release of 2.1.5. This mailing list as a few tips how to deal with the 2.1.x releases, but the best way is indeed a downg

Re: minimum bandwidth requirement between two Geo Redundant sites of Cassandra database

Hi, I would not recommend anything below 1Gbps for the bandwidth. Latency try to have it as low as you can. Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian | Twitter: cjrolo | Linkedin: *linkedin.com/in/carlosjuzarterolo