Re: Cassandra HANGS after some writes

I made one single change in default cassandra.yaml, just to experiment. native_transport_min_threads: *1* native_transport_max_threads: *1* with max one single thread for native protocol requests i noticed some improvement, earlier with default yaml most of time it was failing after * 10K* combin

Re: Recommendation for hosting multi tenant clusters

http://www.mail-archive.com/user@cassandra.apache.org/msg11022.html sums it up pretty well. Optimised images and provisioned IOPS may help, but whatever way you spin it your reads and writes are still going out on the network somewhere. EBS is like a giant SAN which will drop out at any second,

Re: Recommendation for hosting multi tenant clusters

I strongly recommend against EBS, even with optimized & ebs provisioned. The throughput you'll get from local drives is significantly better than what you'll get with EBS (even 4K iops provisioned) On Aug 13, 2013, at 2:10 PM, Rahul Gupta wrote: > I am working on requirement to host multi ten

Re: Upgrade path to 2.0

On Tue, Aug 13, 2013 at 2:58 PM, Randy Fradin wrote: > If I'm reading this right, it seems CASSANDRA-5695 only bumps the > upgrade path to 1.2.7. And is CASSANDRA-5845 still a concern if we > don't make any schema changes while the cluster is in a split version > state? That is my understanding

Re: Upgrade path to 2.0

Thanks, I won't be upgrading to 2.0 any time soon but I would prefer not to have to do a minor 1.2.8->1.2.9 upgrade before I do down the road. If I'm reading this right, it seems CASSANDRA-5695 only bumps the upgrade path to 1.2.7. And is CASSANDRA-5845 still a concern if we don't make any schema

Recommendation for hosting multi tenant clusters

I am working on requirement to host multi tenant Cassandra cluster (or set of clusters) on Amazon EC2 (AWS). With everything else sorted out, I have below question where I am looking for recommendations: Does Amazon's recent support of EBS optimized images changes whole discussion around EBS v

token(), limit and wide rows

HI, ok, so I found token() [1], and that it is an option for paging through randomly partitioned data. I take it that combining token() and LIMIT is the CQL3 idiom for paging (set aside the fact that one shouldn't raelly want to page and use C*) Now, when I page through a CF with wide rows, l

Re: Upgrade path to 2.0

On Tue, Aug 13, 2013 at 11:25 AM, Randy Fradin wrote: > According to the upgrade notes from NEWS.txt, under 2.0.0 it says: > > - Upgrading is ONLY supported from Cassandra 1.2.9 or later. This > goes for sstable compatibility as well as network. When > upgrading from an earlier re

Re: 0.7 node not starting

1) Can't 2) Interesting 3) Interesting 4) Remove all the Hints and OpsCenter data files I used 4 to get it working. On 13 August 2013 11:23, Robert Coli wrote: > On Tue, Aug 13, 2013 at 11:14 AM, Ashley Martens > wrote: > > > INFO [main] 2013-08-13 18:14:13,759 DatabaseDescriptor.java (line

Re: For Multi Datacenter Geo redundancy which snitch works better

On Tue, Aug 13, 2013 at 11:08 AM, Ken Schell wrote: > Could you enlighten me with issues we could expect if we went with > the RackInferringSnitch? It seems the smiplest to maintain when adding > nodes. > Almost no one uses it, so you are not assured that it has been shown to work as expected,

Upgrade path to 2.0

According to the upgrade notes from NEWS.txt, under 2.0.0 it says: - Upgrading is ONLY supported from Cassandra 1.2.9 or later. This goes for sstable compatibility as well as network. When upgrading from an earlier release, upgrade to 1.2.9 first and run upgradesstables befo

Re: 0.7 node not starting

On Tue, Aug 13, 2013 at 11:14 AM, Ashley Martens wrote: > INFO [main] 2013-08-13 18:14:13,759 DatabaseDescriptor.java (line 181) DiskAccessMode 'auto' determined to be mmap, indexAccessMode is mmap > Caused by: java.io.IOError: java.io.IOException: Map failed 1) Upgrade your ancient and broken ve

0.7 node not starting

INFO [main] 2013-08-13 18:14:13,674 AbstractCassandraDaemon.java (line 115) Heap size: 8568963072/8568963072 INFO [main] 2013-08-13 18:14:13,674 AbstractCassandraDaemon.java (line 116) Classpath: /usr/share/cassandra/antlr-3.1.3.jar:/usr/share/cassandra/apache-cassandra-0.7.10.jar:/usr/share/cass

Re: For Multi Datacenter Geo redundancy which snitch works better

Rob, Could you enlighten me with issues we could expect if we went with the RackInferringSnitch? It seems the smiplest to maintain when adding nodes. From: Robert Coli mailto:rc...@eventbrite.com>> Date: Monday, August 12, 2013 12:44 PM To: "user@cassandra.apache.org

Re: Cassandra HANGS after some writes

On Tue, Aug 13, 2013 at 10:34 AM, Andrew Cobley wrote: > Has anyone ever done any performance comparisons of linux vs a headless > windows server ? > No, but given the number of linux specific optimizations in Cassandra, I would expect this to be no contest. =Rob

Re: What's difference between node tool removenode & decommission in 1.2.x

On Tue, Aug 13, 2013 at 10:06 AM, Jasdeep Hundal wrote: > Removenode will stream the data that node is responsible for from other > replicas, and AFAIK is generally used when a node is offline and cannot be > brought back up. > removetoken should only be used if the departing node is unavailable

Re: Cassandra HANGS after some writes

Agreed with Alain, There are a number of reasons that he may be running on windows, a development environment comes to mind,or simply to learn about C* BTW Has anyone ever done any performance comparisons of linux vs a headless windows server ? Andy On 13 Aug 2013, at 17:07, Alain RODRIGUEZ

Re: Cassandra HANGS after some writes

Hi all, I started cassandra few weeks back and i am on development enviornment, it will take months for production as everything in development.But i will spend time and setup one machine with UBuntu and will check if similar problem comes or not...Also i had started hands on Hadoop then linux

Re: What's difference between node tool removenode & decommission in 1.2.x

Thanks for clarification. ;-) --Frank On Aug 13, 2013, at 10:06 AM, Jasdeep Hundal mailto:dsjas...@gmail.com>> wrote: Decommission moves the data from the node being decommissioned to the other nodes that will now have ownership over the data. Removenode will stream the data that node is re

Re: What's difference between node tool removenode & decommission in 1.2.x

Decommission moves the data from the node being decommissioned to the other nodes that will now have ownership over the data. Removenode will stream the data that node is responsible for from other replicas, and AFAIK is generally used when a node is offline and cannot be brought back up. I think

What's difference between node tool removenode & decommission in 1.2.x

I'm a little bit confused on why the nodetool utility has a decommission and a removenode command. I speculate that decommission command just informs the other nodes that I'm going offline and does not move the data off that node. Whereas removenode resync's the data/tokens to the other nodes.

Re: HsHa

I have this anytime I try to switch to "hsha" since 0.8. Always kept "sync" for this reason. Thought I was alone with this bug since I never had any clue about this on the mailing list. So +1. Alain 2013/8/13 Christopher Wirt > Hello, > > ** ** > > I was trying out the hsha thrift server

Re: Cassandra HANGS after some writes

@Kanwar Sangha "Cassandra on windows ? Please install Linux !" Useful comment, please spare your time and stop that troll. He surely have his reason to use windows (I suppose it is a dev constraint or choice). Anyway, C* is available in windows so it should work. Comments like "windows sucks, go

HsHa

Hello, I was trying out the hsha thrift server implementation and found that I get a fair amount of these appearing in the server logs. ERROR [Selector-Thread-9] 2013-08-13 15:39:10,433 TNonblockingServer.java (line 468) Read an invalid frame size of 0. Are you using TFramedTransport on the

RE: Cassandra HANGS after some writes

Cassandra on windows ? Please install Linux ! From: Romain HARDOUIN [mailto:romain.hardo...@urssaf.fr] Sent: 13 August 2013 10:17 To: user@cassandra.apache.org Subject: Re: Cassandra HANGS after some writes Naresh, My two cents is that you should run Cassandra on a Linux VM. Issues are more eas

Re: Cassandra HANGS after some writes

Naresh, My two cents is that you should run Cassandra on a Linux VM. Issues are more easy to diagnose/pinpoint. Windows is a bit obscure to many people here. Cheers Alexis Rodríguez a écrit sur 13/08/2013 16:50:42 : > De : Alexis Rodríguez > A : user@cassandra.apache.org, > Date : 13/08/2

Re: C* 1.0.6 to 1.1.12: upgradesstables or scrub?

Yes, forgot to mention we use LCS in 1.0.6. Thank you. Jeremy Hanna a écrit sur 13/08/2013 16:44:56 : > De : Jeremy Hanna > A : user@cassandra.apache.org, > Date : 13/08/2013 16:45 > Objet : Re: C* 1.0.6 to 1.1.12: upgradesstables or scrub? > > If you were using leveled compaction on any col

Re: Cassandra HANGS after some writes

Naresh, Windows is not my cup of tea. May be someone else has more experience using the Redmond's prodigy child. cheers, and good luck On Tue, Aug 13, 2013 at 11:21 AM, Naresh Yadav wrote: > Hi Alex, > > Yes i am testing in development environment of Windows 7 64bit. > I left default yaml the

Re: C* 1.0.6 to 1.1.12: upgradesstables or scrub?

If you were using leveled compaction on any column families in 1.0, you'll need to run offline scrub on those column families. On 13 Aug 2013, at 15:38, Romain HARDOUIN wrote: > Hi all, > > We are migrating from C* 1.0.6 to 1.1.12 and after reading DataStax > documentation (http://www.datast

C* 1.0.6 to 1.1.12: upgradesstables or scrub?

Hi all, We are migrating from C* 1.0.6 to 1.1.12 and after reading DataStax documentation (http://www.datastax.com/docs/1.1/install/upgrading) we are a bit confused. The section "Completing the Upgrade", step 6, points out: If you are upgrading from Cassandra 1.1.3 or earlier to Cassandra

Re: Cassandra HANGS after some writes

Hi Alex, Yes i am testing in development environment of Windows 7 64bit. I left default yaml then cassandra created "var" folder and created data, log, cache folders in it.I tried commit log on different harddisk but this problem not solved with thatI guess this problem is somewhat related

Re: Cassandra HANGS after some writes

Naresh, are you deploying cassandra in windows? If that is the case you may need to change the data and commitlog directories in cassandra.yaml. Also you should check the log directories. See the section 2.1 http://wiki.apache.org/cassandra/GettingStarted On Tue, Aug 13, 2013 at 8:28 AM, Nares

Re: Cassandra HANGS after some writes

Thanks Alain, will avoid capsi am newbie to cassandra, just started using 2 weeks back.. Here are JConsole screenshots just 5mins after cassandra freezed : http://i.imgur.com/3oUBjKU.png http://i.imgur.com/2O4PrKb.png http://i.imgur.com/zxhFzr1.png 4:05 is time cassandra freezed

Re: cassandra 1.2.5- virtual nodes (num_token) pros/cons?

On 13 August 2013 10:15, Alain RODRIGUEZ wrote: Streaming from all the physical nodes in the cluster should make repair > faster, for the same reason it makes bootstrap faster. Shouldn't it ? > Virtual nodes doesn't speed up either very much. Repair and bootstrap will be limited by the node doi

Re: Cassandra HANGS after some writes

Hi Naresh. First thing, there is no need of caps in here. People reading this ML is here to help when they have time and skills enough to do so. So please, chill out and do not use caps to show how much desperate you are. Concerning your problem, the only abnormal thing I was able to find in your

Cassandra HANGS after some writes

Hi All, I have single node cassandra using CQL using datastax java driver 1.0.1 and cassandra verison 1.2.6. *Infrastructure :* 16GB machine with 8GB heap given to cassandra, i7 processor.. DEFAULT cassandra.yaml no change done by me. -Xms1G^ -Xmx12G^ no other change in cassandra.bat *

Re: cassandra 1.2.5- virtual nodes (num_token) pros/cons?

@Aaron Streaming from all the physical nodes in the cluster should make repair faster, for the same reason it makes bootstrap faster. Shouldn't it ? 2013/8/12 Aaron Morton > Aaron - I read about the virtual nodes at > http://www.datastax.com/dev/blog/virtual-nodes-in-cassandra-1-2 > > > Than

Re: understanding memory footprint

if using 1.2.*, Bloom filters are in native memory so not pressuring your heap, how many data do you have per node ? If this value is big, you have samples index in the heap consuming a lot of memory, for sure, and growing as your data per node grow. Solutions : increase the heap if < 8GB and / or