Re: How can I check cassandra cluster has a real working function of high availability?

On Sat, Jun 15, 2019 at 4:31 PM Nimbus Lin wrote: > Dear cassandra's pioneers: > I am a 5 years' newbie, it is until now that I have time to use > cassandra. but I cann't check cassandra's high availabily when I stop a > seed node or none seed DN as CGE or Greenplum. > Would someone can

Cassandra migration from 1.25 to 3.x

Hi, We are upgrading Cassandra from 1.25 to 3.X. Just curious if there is any recommended open source utility for the same. Regards Anurag

Re: Cassandra migration from 1.25 to 3.x

On Mon, Jun 17, 2019 at 9:30 AM Anurag Sharma wrote: > > We are upgrading Cassandra from 1.25 to 3.X. Just curious if there is any > recommended open source utility for the same. > Hi, The "recommended open source utility" is the Apache Cassandra itself. ;-) Given the huge difference between

Re: Cassandra migration from 1.25 to 3.x

Thanks Alex, I came across some interesting and efficient ways of upgrading from 1.x to 3.x as described in the blog here and others. Was curious if someone has open-sourced their custom utility. :D Regards Anurag On Mon,

Re: Cassandra migration from 1.25 to 3.x

First and foremost, read NEWS.txt from your current version to the version you wish to upgrade to. There are too may details that you many need to be aware of. For instance, in the 2.0.0 Upgrading notes: https://github.com/apache/cassandra/blob/cassandra-3.11/NEWS.txt#L1169-L1178 I assume you

RE: [EXTERNAL] Re: Cassandra migration from 1.25 to 3.x

The advice so far is exactly correct for an in-place kind of upgrade. The blog post you mentioned is different. They decided to jump versions in Cassandra by standing up a new cluster and using a dual-write/dual-read process for their app. They also wrote code to read and interpret sstables in o

Compaction resume after node restart and upgrade

Hi, C* version 3.0.16. Two questions: 1. If major compaction is in progress and we restart the node, will compaction start from beginning or will it resume from where the node was shut down? 2. If we upgrade binaries to C* 4.0 while compaction is running, will it resume the compaction or start ove

Re: Compaction resume after node restart and upgrade

> On Jun 17, 2019, at 4:22 PM, Nitan Kainth wrote: > > Hi, > > C* version 3.0.16. > Two questions: > 1. If major compaction is in progress and we restart the node, will > compaction start from beginning or will it resume from where the node was > shut down? You’ll have to restart it manuall

Re: Compaction resume after node restart and upgrade

Thanks Jeff! Regards, Nitan Cell: 510 449 9629 > On Jun 17, 2019, at 7:15 PM, Jeff Jirsa wrote: > > > >> On Jun 17, 2019, at 4:22 PM, Nitan Kainth wrote: >> >> Hi, >> >> C* version 3.0.16. >> Two questions: >> 1. If major compaction is in progress and we restart the node, will >> compact

Re: Compaction resume after node restart and upgrade

The interim/temp sstable will delete by itself? Regards, Nitan Cell: 510 449 9629 > On Jun 17, 2019, at 7:15 PM, Jeff Jirsa wrote: > > > >> On Jun 17, 2019, at 4:22 PM, Nitan Kainth wrote: >> >> Hi, >> >> C* version 3.0.16. >> Two questions: >> 1. If major compaction is in progress and we

Re: Compaction resume after node restart and upgrade

Yes - the incomplete sstable will be deleted during startup (in 3.0 and newer there’s a transaction log of each compaction in progress - that gets cleaned during the startup process) > On Jun 17, 2019, at 6:02 PM, Nitan Kainth wrote: > > The interim/temp sstable will delete by itself? > > >

Re: Compaction resume after node restart and upgrade

Thanks Jeff. On Mon, Jun 17, 2019 at 8:08 PM Jeff Jirsa wrote: > Yes - the incomplete sstable will be deleted during startup (in 3.0 and > newer there’s a transaction log of each compaction in progress - that gets > cleaned during the startup process) > > On Jun 17, 2019, at 6:02 PM, Nitan Kain

Cassandra Tombstone

Hi, I am using Cassandra cluster with 3 nodes which is hosted on AWS. Also we have NodeJS web Application which is on AWS ELB. Now the issue is that, when I add 2 or more servers (nodeJS) in AWS ELB then the delete queries are not working on Cassandra. Its working when there is only one server in

Re: Cassandra Tombstone

This is nearly impossible to answer without much more info, but suspect you’re either: Using very weak consistency levels or some weirdness with data centers / availability zones (like simplestrategy and local_*), or Have bad clocks / no ntp / wrong time zones, > On Jun 17, 2019, at 11:05 PM,