Re: missing rows while importing data using sstable loader

What is the best practise to create sstables? On 1 February 2016 at 15:21, Romain Hardouin wrote: > Did you run "nodetool flush" on the source node? If not, the missing rows > could be in memtables. >

Extensions

Greetings, Is it a way to find out (list or otherwise) if any extensions were installed with Cassandra base package? Thanks, Oleg

Re: EC2 storage options for C*

Ah, yes, the good old days of m1.large. -- Jack Krupansky On Mon, Feb 1, 2016 at 5:12 PM, Jeff Jirsa wrote: > A lot of people use the old gen instances (m1 in particular) because they > came with a ton of effectively free ephemeral storage (up to 1.6TB). > Whether or not they’re viable is a dec

Re: EC2 storage options for C*

Hi Jeff, I'm going to go back and review your presentation. I missed it at Cassandra Summit and didn't make it to re:Invent last year. The opinion I voiced was from my own direct experience. Didn't mean to imply that there weren't other good options available. Thanks, Steve On Mon, Feb 1, 2016 a

Re: EC2 storage options for C*

A lot of people use the old gen instances (m1 in particular) because they came with a ton of effectively free ephemeral storage (up to 1.6TB). Whether or not they’re viable is a decision for each user to make. They’re very, very commonly used for C*, though. At a time when EBS was not sufficient

Re: EC2 storage options for C*

Yeah, I would only start a previous-generation instance for non-production purposes at this point and I suspect that many of them will be retired sooner or later. Given a choice, I'd use i2 instances for most purposes, and use the d2 instances where storage volume and access patterns demanded it.

Re: EC2 storage options for C*

Thanks. My typo - I referenced "C2 Dense Storage" which is really "D2 Dense Storage". The remaining question is whether any of the "Previous Generation Instances" should be publicly recommended going forward. And whether non-SSD instances should be recommended going forward as well. sure, technic

Re: Questions about the replicas selection and remote coordinator

Hi Steve, Thank you so much for your kind reply and now it makes more sense. But for the remote coordinator issue, it’s definitely a interesting topic. If you have any other conclusion on this. I’d be pretty happy to learn from you. Thanks again! Jun > On Jan 29, 2016, at 13:09, Stev

Re: EC2 storage options for C*

Hi Jack, At the bottom of the instance-types page, there is a link to the previous generations, which includes the older series (m1, m2, etc), many of which have HDD options. There are also the d2 (Dense Storage) instances in the current generation that include various combos of local HDDs. The

Re: EC2 storage options for C*

Thanks. Reading a little bit on AWS, and back to my SSD vs. magnetic question, it seems like magnetic (HDD) is no longer a recommended storage option for databases on AWS. In particular, only the C2 Dense Storage instances have local magnetic storage - all the other instance types are SSD or EBS-on

Re: Moving Away from Compact Storage

Use Apache Spark to parallelize the data migration. Look at this piece of code https://github.com/doanduyhai/Cassandra-Spark-Demo/blob/master/src/main/scala/usecases/MigrateAlbumsData.scala#L58-L60 If your source and target tables have the SAME structure (except for the COMPACT STORAGE clause), mi

Moving Away from Compact Storage

Hi Whats the fastest and reliable way to migrate data from a Compact Storage table to Non-Compact storage table? I was not able to find any command for dropping the compact storage directive..so I think migrating data is the only way...any suggestions? ThanksAnuj

Re: EC2 storage options for C*

> My apologies if my questions are actually answered on the video or slides, I > just did a quick scan of the slide text. Virtually all of them are covered. > I'm curious where the EBS physical devices actually reside - are they in the > same rack, the same data center, same availability zone?

Re: Session timeout

Jeff, You mentioned that both Authentication and Authorization are pluggable. In relation to that, is logging pluggable as well? I.e. if I'm not happy with what logback has to provide and want to replace it with some alternative logging module, can I do it? Thanks, Oleg On Fri, Jan 29, 2016 at

Re: Cassandra's log is full of mesages reset by peers even without traffic

Hello Annuj,, I checked my settings and this what I got. root@node001[SPH][BENCH][PnS3]:~$ sysctl -A | grep net.ipv4 | grep net.ipv4.tcp_keepalive_probes net.ipv4.tcp_keepalive_probes = 9 root@node001[SPH][BENCH][PnS3]:~$ sysctl -A | grep net.ipv4 | grep net.ipv4.tcp_keepalive_intvl net.ipv4.tcp_k

Re: missing rows while importing data using sstable loader

Did you run "nodetool flush" on the source node? If not, the missing rows could be in memtables.

Re: cassandra-stress tool - InvalidQueryException: Batch too large

Yeah that looks like a bug. Can you open a JIRA and attach the full .yaml? Thanks! On Mon, Feb 1, 2016 at 5:09 AM, Ralf Steppacher wrote: > I am using Cassandra 2.2.4 and I am struggling to get the cassandra-stress > tool to work for my test scenario. I have followed the example on > http://w

Re: EC2 storage options for C*

Oops... that was supposed to be "not a fan of video"! I have no problem with the guys in the video! -- Jack Krupansky On Mon, Feb 1, 2016 at 8:51 AM, Jack Krupansky wrote: > I'm not a fan of guy - this appears to be the slideshare corresponding to > the video: > > http://www.slideshare.net/Amaz

Re: EC2 storage options for C*

I'm not a fan of guy - this appears to be the slideshare corresponding to the video: http://www.slideshare.net/AmazonWebServices/bdt323-amazon-ebs-cassandra-1-million-writes-per-second My apologies if my questions are actually answered on the video or slides, I just did a quick scan of the slide t

Asynchronous, one-way data replication to stand-alone nodes?

Hello. I am not sure this have been asked before. I've tried to search and either I am terrible at searching, or the question haven't been asked. We are trying to figure out how to solve the following problem; We have systems in various regions in AWS, and we are trying to find a way to

cassandra-stress tool - InvalidQueryException: Batch too large

I am using Cassandra 2.2.4 and I am struggling to get the cassandra-stress tool to work for my test scenario. I have followed the example on http://www.datastax.com/dev/blog/improved-cassandra-2-1-stress-tool-benchmark-any-schema

Re: Can't select count(*)

Regarding select count(*), the timeout is probably client side. Try changing the default connect timeout in cqlsh via --request-timeout. By default it is 10 seconds. Refer to "cqlsh --help" for more details but basically "cqlsh --request-timeout=30" should work. Regarding COPY TO/FROM, these comma