Re: Cassandra upgrade from 3.11.3 -> 3.11.6

te out the admin tasks so >>>> that I can reason what should happen. I would either scale up or upgrade >>>> (depending on which is more urgent), then do the other. >>>> >>>> >>>> >>>> >>>> >>>> Sean Durity >

Re: Cassandra upgrade from 3.11.3 -> 3.11.6

up or upgrade >>> (depending on which is more urgent), then do the other. >>> >>> >>> >>> >>> >>> Sean Durity >>> >>> >>> >>> *From:* manish khandelwal >>> *Sent:* Wednesday, June 24, 2020 5:52

Re: Cassandra upgrade from 3.11.3 -> 3.11.6

he admin tasks so >> that I can reason what should happen. I would either scale up or upgrade >> (depending on which is more urgent), then do the other. >> >> >> >> >> >> Sean Durity >> >> >> >> *From:* manish khandelwal >>

RE: Cassandra upgrade from 3.11.3 -> 3.11.6

@cassandra.apache.org Subject: [EXTERNAL] Re: Cassandra upgrade from 3.11.3 -> 3.11.6 Thank you all for the suggestions. I am not trying to scale up the cluster for capacity but for the upgrade process instead of in place upgrade I am planning to add nodes with 3.11.6 and then decommiss

Re: Cassandra upgrade from 3.11.3 -> 3.11.6

> that I can reason what should happen. I would either scale up or upgrade > (depending on which is more urgent), then do the other. > > > > > > Sean Durity > > > > *From:* manish khandelwal > *Sent:* Wednesday, June 24, 2020 5:52 AM > *To:* user@cassandra.ap

RE: Cassandra upgrade from 3.11.3 -> 3.11.6

that I can reason what should happen. I would either scale up or upgrade (depending on which is more urgent), then do the other. Sean Durity From: manish khandelwal Sent: Wednesday, June 24, 2020 5:52 AM To: user@cassandra.apache.org Subject: [EXTERNAL] Re: Cassandra upgrade from 3.11.3 -> 3.1

Re: Cassandra upgrade from 3.11.3 -> 3.11.6

> > Can I add new nodes with the 3.11.6 version to the cluster running with > 3.11.3? > Technically you can. You'll be able to add 3.11.6 nodes to a 3.11.3 cluster. In fact, the reverse works too in my tests but I personally wouldn't want to do it in production. > Also, I see the SSTable

Re: Cassandra upgrade from 3.11.3 -> 3.11.6

Rightly said by Surbhi, it is not good to scale with mixed versions as debugging issues will be very difficult. Better to upgrade first and then scale. Regards On Wed, Jun 24, 2020 at 11:20 AM Surbhi Gupta wrote: > In case of any issue, it gets very difficult to debug when we have > multiple

Re: Cassandra upgrade from 3.11.3 -> 3.11.6

In case of any issue, it gets very difficult to debug when we have multiple versions. On Tue, 23 Jun 2020 at 22:23, Jürgen Albersdorfer wrote: > Hi, I would say „It depends“ - as it always does. I have had a 21 Node > Cluster running in Production in one DC with versions ranging from 3.11.1 >

Re: Cassandra upgrade from 3.11.3 -> 3.11.6

Hi, I would say „It depends“ - as it always does. I have had a 21 Node Cluster running in Production in one DC with versions ranging from 3.11.1 to 3.11.6 without having had any single issue for over a year. I just upgraded all nodes to 3.11.6 for the sake of consistency. Von meinem iPhone

Re: Cassandra upgrade from 3.11.3 -> 3.11.6

Hi , We have recently upgraded from 3.11.0 to 3.11.5 . There is a sstable format change from 3.11.4 . We also had to expand the cluster and we also discussed about expansion first and than upgrade. But finally we upgraded and than expanded. As per our experience what I could tell you is, it is

Cassandra upgrade from 3.11.3 -> 3.11.6

Hello, I am trying to upgrade from 3.11.3 to 3.11.6. Can I add new nodes with the 3.11.6 version to the cluster running with 3.11.3? Also, I see the SSTable format changed from mc-* to md-*, does this cause any issues?

Re: [EXTERNAL] Apache Cassandra upgrade path

des. > > > > > > Sean Durity – Staff Systems Engineer, Cassandra > > > > *From:* Alok Dwivedi > *Sent:* Friday, July 26, 2019 3:21 PM > *To:* user@cassandra.apache.org > *Subject:* Re: [EXTERNAL] Apache Cassandra upgrade path > > > > Hi Sean > >

Re: [EXTERNAL] Apache Cassandra upgrade path

: Alok Dwivedi Sent: Friday, July 26, 2019 3:21 PM To: user@cassandra.apache.org Subject: Re: [EXTERNAL] Apache Cassandra upgrade path   Hi Sean The recommended practice for upgrade is to explicitly control protocol version in your application during upgrade process. Basically the protocol version

Re: [EXTERNAL] Apache Cassandra upgrade path

een > nodes. > > > > > > Sean Durity – Staff Systems Engineer, Cassandra > > > > *From:* Alok Dwivedi > *Sent:* Friday, July 26, 2019 3:21 PM > *To:* user@cassandra.apache.org > *Subject:* Re: [EXTERNAL] Apache Cassandra upgrade path > > &

RE: [EXTERNAL] Apache Cassandra upgrade path

This would handle client protocol, but not streaming protocol between nodes. Sean Durity – Staff Systems Engineer, Cassandra From: Alok Dwivedi Sent: Friday, July 26, 2019 3:21 PM To: user@cassandra.apache.org Subject: Re: [EXTERNAL] Apache Cassandra upgrade path Hi Sean The recommended

Re: [EXTERNAL] Apache Cassandra upgrade path

> quickly as possible. Don’t stay in a mixed state very long. The cluster >> will function fine in a mixed state – except for those streaming >> operations. No repairs, no bootstraps. >> >> >> >> >> >> Sean Durity – Staff Systems Engineer, Cassandra &

Re: [EXTERNAL] Apache Cassandra upgrade path

Dhanwada > *Sent:* Friday, July 26, 2019 2:24 PM > *To:* user@cassandra.apache.org > *Subject:* [EXTERNAL] Apache Cassandra upgrade path > > > > Hello, > > > > I am trying to upgrade Apache Cassandra from 2.1.16 to 3.11.3, the regular > rolling upgrade process works fine

RE: [EXTERNAL] Apache Cassandra upgrade path

Rao Dhanwada Sent: Friday, July 26, 2019 2:24 PM To: user@cassandra.apache.org Subject: [EXTERNAL] Apache Cassandra upgrade path Hello, I am trying to upgrade Apache Cassandra from 2.1.16 to 3.11.3, the regular rolling upgrade process works fine without any issues. However, I am running

Apache Cassandra upgrade path

Hello, I am trying to upgrade Apache Cassandra from 2.1.16 to 3.11.3, the regular rolling upgrade process works fine without any issues. However, I am running into an issue where if there is a node with older version dies (hardware failure) and a new node comes up and tries to bootstrap, it's

RE: [EXTERNAL] Cassandra Upgrade Plan 2.2.4 to 3.11.3

is now obsolete. Test thoroughly, then go forward as quickly as possible. Sean Durity From: Devaki, Srinivas Sent: Sunday, December 02, 2018 9:24 AM To: user@cassandra.apache.org Subject: [EXTERNAL] Cassandra Upgrade Plan 2.2.4 to 3.11.3 Hi everyone, I have planned out our org's cassandra

Cassandra Upgrade Plan 2.2.4 to 3.11.3

Hi everyone, I have planned out our org's cassandra upgrade plan and want to make sure if it seems fine. Details Existing Cluster: * Cassandra 2.2.4 * 8 nodes with 32G ram and 12G max heap allocated to cassandra * 4 nodes in each rack 1. Ensured all clients to use LOCAL_* consistency levels

Re: Lost counter updates during Cassandra upgrade 2.2.11 to 3.11.2

Hi, I haven't investigated the issue further. -- Konrad On Sat, Nov 10, 2018, at 05:49, Laxmikant Upadhyay wrote: > Hi, > > I have faced similar issue while upgrading from 2.1.16 -> 3.11.2 in a > 3 node cluster.> I have raised jira ticket CASSANDRA-14881[1] for this issue > , but have

Re: Lost counter updates during Cassandra upgrade 2.2.11 to 3.11.2

Hi, I have faced similar issue while upgrading from 2.1.16 -> 3.11.2 in a 3 node cluster. I have raised jira ticket CASSANDRA-14881 for this issue , but have not got any response on this yet. @Konrad did you get any resolution on this ?

Lost counter updates during Cassandra upgrade 2.2.11 to 3.11.2

Hi, During rolling upgrade of our cluster we noticed that some updates on table with counters were not being applied. It looked as if it depended on whether coordinator handling request was already upgraded or not. I observed similar behavior while using cqlsh and executing queries manually.

Re: Cassandra Upgrade with Different Protocol Version

> On Jul 5, 2018, at 12:45 PM, Anuj Wadehra > wrote: > > Hi, > > I woud like to know how people are doing rolling upgrade of Casandra clustes > when there is a change in native protocol version say from 2.1 to 3.11. > During rolling upgrade, if client application is restarted on nodes,

Re: Cassandra Upgrade with Different Protocol Version

There is replication between 2.1 and 3.x, but not hints. You will have to repair past the window, but you should be doing that anyway if you care about tombstones doing the right thing Read quorum with 2/3 in either version should work fine - if it gives you an error please open a JIRA with

Re: Cassandra Upgrade with Different Protocol Version

other concerns: there is no replication between 2.11 and 3.11, store in hints, and replay hints when remote is same version. have to do repair if over window. if read quorum 2/3, will get error. in case rollback to 2.11, can not read new version 3.11 data files, but online rolling upgrade, some

Re: Cassandra Upgrade with Different Protocol Version

Hello Anuj, The 2nd workaround should work. As app will auto discover all the other nodes. Its the first contact with the node that app makes determines the protocol version. So if you remove the newer version nodes from the app configuration after the startup, it will auto discover the newer

Cassandra Upgrade with Different Protocol Version

Hi, I woud like to know how people are doing rolling upgrade of Casandra clustes when there is a change in native protocol version say from 2.1 to 3.11. During rolling upgrade, if client application is restarted on nodes, the client driver may first contact an upgraded Cassandra node with v4

Re: Cassandra upgrade from 2.1 to 3.0

We are using datstax java driver  1.5.0 Thank you. On Saturday, 12 May 2018, 10:37:04 GMT-7, Jeff Jirsa wrote: I haven't seen this before, but I have a guess. What client/driver are you using? Are you using a prepared statement that has every column listed for the

Re: Cassandra upgrade from 2.1 to 3.0

I haven't seen this before, but I have a guess. What client/driver are you using? Are you using a prepared statement that has every column listed for the update, and leaving the un-set columns as null? If so, the null is being translated into a delete, which is clearly not what you want. The

Re: Cassandra upgrade from 2.1 to 3.0

After further analyzing the data. I see some pattern. The rows which were updated in last 2-3 weeks, the column which were not part of this update have the null values.  Has anyone encountered this issue during the upgrade? Thank you, On Thursday, 10 May 2018, 19:49:50 GMT-7,

Re: Cassandra upgrade from 2.1 to 3.0

Hello Jeff, 2.1.19 to 3.0.15. Thank you. On Thursday, 10 May 2018, 17:43:58 GMT-7, Jeff Jirsa wrote: Which minor version of 3.0 -- Jeff Jirsa On May 11, 2018, at 2:54 AM, kooljava2 wrote: Hello, Upgraded Cassandra 2.1 to 3.0.  We

Re: Cassandra upgrade from 2.1 to 3.0

Which minor version of 3.0 -- Jeff Jirsa > On May 11, 2018, at 2:54 AM, kooljava2 wrote: > > > Hello, > > Upgraded Cassandra 2.1 to 3.0. We see certain data in few columns being set > to "null". These null columns were created during the row creation time. >

RE: Cassandra upgrade from 2.2.8 to 3.10

: Wednesday, March 28, 2018 1:58 PM To: user@cassandra.apache.org Subject: Re: Cassandra upgrade from 2.2.8 to 3.10 You can perform an upgrade from 2.2.x straight to 3.11.2, but the op suggests adding nodes in 3.10 to a cluster that runs 2.2.8, which is why Jeff says it won't work. I see no reason

Re: Cassandra upgrade from 2.2.8 to 3.10

onfirm that such upgrade is supported. If yes, where can I > find official documentation showing upgrade path across releases. > > > https://stackoverflow.com/questions/42094935/apache-cassandra-upgrade-3-x-from-2-1 > > Thanks > > On Mon, Aug 7, 2017 at 5:58 PM, ZAIDI, ASAD A <

Re: Cassandra upgrade from 2.2.8 to 3.10

, where can I find official documentation showing upgrade path across releases. https://stackoverflow.com/questions/42094935/apache-cassandra-upgrade-3-x-from-2-1 Thanks On Mon, Aug 7, 2017 at 5:58 PM, ZAIDI, ASAD A <az1...@att.com> wrote: > Hi folks, I’ve question on upgrade method I’m

Re: Cassandra Upgrade and Driver compatibility

I don’t have a good answer for the driver question, but for versions: Please go to at least 3.0.15, if you can wait a few weeks for 3.0.16 that’s even better -- Jeff Jirsa > On Dec 21, 2017, at 6:47 PM, Mokkapati, Bhargav (Nokia - IN/Chennai) > wrote: > > Hi

Cassandra Upgrade and Driver compatibility

Hi All, We are planning to upgrade the Apache Cassandra and CPP driver as below. Cassandra service version : Old - cassandra-3.0.6-1.noarch.rpm New - cassandra-3.0.13-1.noarch.rpm Cassandra driver version : Old - cassandra-cpp-driver-2.4.3-1.el7.centos.x86_64.rpm New -

Re: Running repair while Cassandra upgrade 2.0.X to 2.1.X

That ticket says that streaming SSTables that are older versions is supported. Streaming is only one component of repairs, and this ticket doesn't talk about repair at all, only bootstrap. For the most part it should work but as Alain said, it's probably best avoided. Especially if you can avoid

Re: Running repair while Cassandra upgrade 2.0.X to 2.1.X

Thanks Alain !! During Cassandra upgrade, we halt repair scheduling for 24 hours as this is good time to finish upgradesstables..we dont want continuous manual monitoring of upgradesstables and then rescheduling of repair tasks when upgradesstables successfully finishes on all the nodes..Here

Re: Running repair while Cassandra upgrade 2.0.X to 2.1.X

Hi Shini, First thing that comes to my mind honestly is "why?". Why would you do this? It's way safer to finish upgrade then repair I would say. That being said, I can make guesses for you here, but the best would probably be to test it. 1. Running nodetool repair on one of the nodes while

Re: Running repair while Cassandra upgrade 2.0.X to 2.1.X

Hi Can someone please answer this query? Thanks On Wed, Dec 6, 2017 at 9:58 AM, shini gupta wrote: > If we have upgraded Cassandra binaries from 2.0 to 2.1 on ALL the nodes > but upgradesstable is still pending, please provide the impact of following > scenarios: > > > >

Running repair while Cassandra upgrade 2.0.X to 2.1.X

If we have upgraded Cassandra binaries from 2.0 to 2.1 on ALL the nodes but upgradesstable is still pending, please provide the impact of following scenarios: 1. Running nodetool repair on one of the nodes while upgradesstables is still executing on one or more nodes in the cluster. 2. Running

Re: Cqlsh unable to switch keyspace after Cassandra upgrade.

Yesterday found problem source. It was because of old cassandra-driver for python language. Driver removal and pip install solved the issue. 2017-11-02 20:33 GMT+07:00 Blake Eggleston : > Looks like a bug, could you open a jira? > > > On Nov 2, 2017, at 2:08 AM, Mikhail

Re: Cqlsh unable to switch keyspace after Cassandra upgrade.

Looks like a bug, could you open a jira? > On Nov 2, 2017, at 2:08 AM, Mikhail Tsaplin wrote: > > Hi, > I've upgraded Cassandra from 2.1.6 to 3.0.9 on three nodes cluster. After > upgrade > cqlsh shows following error when trying to run "use {keyspace};" command: >

Cqlsh unable to switch keyspace after Cassandra upgrade.

Hi, I've upgraded Cassandra from 2.1.6 to 3.0.9 on three nodes cluster. After upgrade cqlsh shows following error when trying to run "use {keyspace};" command: 'ResponseFuture' object has no attribute 'is_schema_agreed' Actual upgrade was done on Ubuntu 16.04 by running "apt-get upgrade

Re: Cassandra upgrade from 2.2.8 to 3.10

Use 3.11.0, instead of 3.10 too - has bug fixes on top of 3.10 and gets long term release support. -- Michael On 08/07/2017 05:09 PM, Jeff Jirsa wrote: > Cant really stream cross-version. You need to add nodes and then upgrade > them (or upgrade all the nodes, and then add new ones). > > > On

Re: Cassandra upgrade from 2.2.8 to 3.10

Cant really stream cross-version. You need to add nodes and then upgrade them (or upgrade all the nodes, and then add new ones). On Mon, Aug 7, 2017 at 2:58 PM, ZAIDI, ASAD A wrote: > Hi folks, I’ve question on upgrade method I’m thinking to execute. > > > > I’m planning from

Cassandra upgrade from 2.2.8 to 3.10

Hi folks, I’ve question on upgrade method I’m thinking to execute. I’m planning from apache-Cassandra 2.2.8 to release 3.10. My Cassandra cluster is configured like one rack with two Datacenters like: 1. DC1 has 4 nodes 2. DC2 has 16 nodes We’re adding another 12 nodes and would

Re: Cassandra Upgrade

Thanks for the info Kurt, I guess I'd go with the normal upgrade procedure then. Thanks again for the help everyone. Shalom Sagges DBA T: +972-74-700-4035 We Create Meaningful

Re: Cassandra Upgrade

Why would you remove all the data? That doesn't sound like a good idea. Just upgrade the OS and then go through the normal upgrade flow of starting C* with the next version and upgrading sstables. Also, *you will need to go from 2.0.14 -> 2.1.16 -> 2.2.8* and upgrade sstables at each stage of the

Re: Cassandra Upgrade

Thanks Ben and Brooke! @Brooke, I'd like to do that because I want to install Centos 7 on those machines instead of the current Centos 6. To achieve that, I need to make a new installation of the OS, meaning taking the server down. So if that's the case, and I can't perform the upgrade online, why

Re: Cassandra Upgrade

Hi Shalom. That seems like the long way around doing it. If you clear the data from the node then add it back in then you will have to restream and recompact the data again for each node. Is there a particular reason why you would need to do it this way? The way we do it is to update Cassandra

Re: Cassandra Upgrade

Hi Shalom, There is a pretty good write up of the procedure written up here ( https://docs.datastax.com/en/upgrade/doc/upgrade/cassandra/upgrdCassandraDetails.html). Things to highlight are: - Don't have a repair running while carrying out the upgrade (so that does timebox your upgrade).

Cassandra Upgrade

Hi Everyone, Hypothetically speaking, can I add a new node with version 2.2.8 to a 2.0.14 cluster? Meaning, instead of upgrading the cluster, I'd like to remove a node, clear all its data, install 2.2.8 and add it back to the cluster, with the process eventually performed on all nodes one by one.

Re: Cassandra Upgrade 3.0.x vs 3.x (Tick-Tock Release)

e: >> >> On Mon, Mar 14, 2016 at 12:40 PM, Kathiresan S < >> <kathiresanselva...@gmail.com>kathiresanselva...@gmail.com> wrote: >> >>> We are planning for Cassandra upgrade in our production environment. >>> Which version of Cassandra is stable and is

Re: Cassandra Upgrade 3.0.x vs 3.x (Tick-Tock Release)

I think that it's not ready, since it has critical bugs. See emails about C* memory leaks On 03/15/2016 01:15 AM, Robert Coli wrote: On Mon, Mar 14, 2016 at 12:40 PM, Kathiresan S <kathiresanselva...@gmail.com <mailto:kathiresanselva...@gmail.com>> wrote:

Re: Cassandra Upgrade 3.0.x vs 3.x (Tick-Tock Release)

n, Mar 14, 2016 at 12:40 PM, Kathiresan S < > kathiresanselva...@gmail.com> wrote: > >> We are planning for Cassandra upgrade in our production environment. >> Which version of Cassandra is stable and is advised to upgrade to, at the >> moment? >> > > > h

Re: Cassandra Upgrade 3.0.x vs 3.x (Tick-Tock Release)

are planning for Cassandra upgrade in our production environment. Which version of Cassandra is stable and is advised to upgrade to, at the moment? https://www.eventbrite.com/engineering/what-version-of-cassandra-should-i-run/ (IOW, you should run either 2.1.MAX or 2.2.5) Relatively soon

Re: Cassandra Upgrade 3.0.x vs 3.x (Tick-Tock Release)

On Mon, Mar 14, 2016 at 12:40 PM, Kathiresan S <kathiresanselva...@gmail.com > wrote: > We are planning for Cassandra upgrade in our production environment. > Which version of Cassandra is stable and is advised to upgrade to, at the > moment? > https://www.eventbrite.com/engine

Re: Cassandra Upgrade 3.0.x vs 3.x (Tick-Tock Release)

<kathiresanselva...@gmail.com > wrote: > Hi, > > We are planning for Cassandra upgrade in our production environment. > Which version of Cassandra is stable and is advised to upgrade to, at the > moment? > > Looking at this JIRA (CASSANDRA-10822 > <https://issues.apach

Cassandra Upgrade 3.0.x vs 3.x (Tick-Tock Release)

Hi, We are planning for Cassandra upgrade in our production environment. Which version of Cassandra is stable and is advised to upgrade to, at the moment? Looking at this JIRA (CASSANDRA-10822 <https://issues.apache.org/jira/browse/CASSANDRA-10822>), it looks like, if at all we plan to u

Blog post with Cassandra upgrade tips

for future major upgrades: http://monkeys.chaordic.com.br/operation/zero-downtime-cassandra-upgrade/ Cheers, -- *Paulo Motta* Chaordic | *Platform* *www.chaordic.com.br http://www.chaordic.com.br/* +55 48 3232.3200

Re: Cassandra upgrade issues...

The first thing I would check is if nodetool is using the right jar. I sounds a lot like if the server has been correctly updated but nodetool haven't and still use the old classes. Check the nodetool executable, it's a shell script, and try echoing the CLASSPATH in there and check it correctly

Re: Cassandra upgrade issues...

Hi Sylvain, Simple as that!!! Using the 1.1.5 nodetool version works as expected. My mistake. Many thanks, Brian On Thu, Nov 1, 2012 at 8:24 AM, Sylvain Lebresne sylv...@datastax.comwrote: The first thing I would check is if nodetool is using the right jar. I sounds a lot like if the

Re: Cassandra upgrade issues...

Note that 1.0.7 came out before 1.1 and I know there were some compatibility issues that were fixed in later 1.0.x releases which could affect your upgrade. I think it would be best to first upgrade to the latest 1.0.x release, and then upgrade to 1.1.x from there. -Bryan On Thu, Nov 1, 2012

Re: Losing keyspace on cassandra upgrade

Have you tried nodetool resetlocalschema on the 1.1.5 ? Cheers - Aaron Morton Freelance Developer @aaronmorton http://www.thelastpickle.com On 20/09/2012, at 11:41 PM, Thomas Stets thomas.st...@gmail.com wrote: A follow-up: Currently I'm back on version 1.1.1. I tried -

Re: Losing keyspace on cassandra upgrade

On Fri, Sep 21, 2012 at 10:39 AM, aaron morton aa...@thelastpickle.comwrote: Have you tried nodetool resetlocalschema on the 1.1.5 ? Yes, I tried a resetlocalschema, and a repair. This didn't change anything. BTW I could find no documentation, what a resetlocalschema actually does...

Re: Losing keyspace on cassandra upgrade

On Wed, Sep 19, 2012 at 5:12 PM, Michael Kjellman mkjell...@barracuda.comwrote: Sounds like you are loosing your system keyspace. When you say nothing important changed between yaml files do you mean with or without your changes? I compared the 1.1.1 cassandra.yaml (with my changes) to the

Re: Losing keyspace on cassandra upgrade

A follow-up: Currently I'm back on version 1.1.1. I tried - unsuccessfully - the following things: 1. Create the missing keyspace on the 1.1.5 node, then copy the files back into the data directory. This failed, since the keyspace was already known on the other node in the cluster. 2. shut

Losing keyspace on cassandra upgrade

I consistently keep losing my keyspace on upgrading from cassandra 1.1.1 to 1.1.5 I have the same cassandra keyspace on all our staging systems: development: a 3-node cluster integration: a 3-node cluster QS: a 2-node cluster (productive will be a 4-node cluster, which is as yet not active)

Re: Losing keyspace on cassandra upgrade

Sounds like you are loosing your system keyspace. When you say nothing important changed between yaml files do you mean with or without your changes? Did your data directories change in the migration? Permissions okay? I've done a 1.1.1 to 1.1.5 upgrade on many of my nodes without issue.. On

Re: Losing keyspace on cassandra upgrade

We've seen that before too - supposedly it was fixed in 1.1.5. Your experience casts some doubt on that. Our workaround, thus far, is to shut down the entire ring and then bring each node back up starting with known good. Then you do nodetool resetlocalschema on the node that's confused and

Re: Losing keyspace on cassandra upgrade

@Edward Do you have a bug number for that by chance? On Sep 19, 2012, at 8:25 AM, Edward Sargisson edward.sargis...@globalrelay.netmailto:edward.sargis...@globalrelay.net wrote: We've seen that before too - supposedly it was fixed in 1.1.5. Your experience casts some doubt on that. Our

Re: Losing keyspace on cassandra upgrade

https://issues.apache.org/jira/browse/CASSANDRA-4583 On 12-09-19 08:30 AM, Michael Kjellman wrote: @Edward Do you have a bug number for that by chance? On Sep 19, 2012, at 8:25 AM, Edward Sargisson edward.sargis...@globalrelay.netmailto:edward.sargis...@globalrelay.net wrote: We've seen that

Re: Cassandra upgrade 1.1.4 issue

I have upgraded jdk from 1.6_u14 to 1.7_u06 and now its working. Thanks Regards *Adeel**Akbar* On 8/24/2012 8:50 PM, Eric Evans wrote: On Fri, Aug 24, 2012 at 5:00 AM, Adeel Akbar adeel.ak...@panasiangroup.com wrote: I have upgraded cassandra on ring and one node successfully upgraded

Cassandra upgrade 1.1.4 issue

Hi, I have upgraded cassandra on ring and one node successfully upgraded first node. On second node I got following error. Please help me to resolve this issue. [root@X]# /u/cassandra/apache-cassandra-1.1.4/bin/cassandra -f xss = -ea

Re: Cassandra upgrade 1.1.4 issue

On Fri, Aug 24, 2012 at 5:00 AM, Adeel Akbar adeel.ak...@panasiangroup.com wrote: I have upgraded cassandra on ring and one node successfully upgraded first node. On second node I got following error. Please help me to resolve this issue. [root@X]#

Re: Concerns about Cassandra upgrade from 1.0.6 to 1.1.X

It's always a good idea to have a read of the NEWS.txt file https://github.com/apache/cassandra/blob/cassandra-1.1/NEWS.txt Cheers - Aaron Morton Freelance Developer @aaronmorton http://www.thelastpickle.com On 12/07/2012, at 5:51 PM, Tyler Hobbs wrote: On Wed, Jul 11, 2012 at

Re: Concerns about Cassandra upgrade from 1.0.6 to 1.1.X

-about-Cassandra-upgrade-from-1-0-6-to-1-1-X-tp7581197p7581221.html Sent from the cassandra-u...@incubator.apache.org mailing list archive at Nabble.com.

Concerns about Cassandra upgrade from 1.0.6 to 1.1.X

this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Concerns-about-Cassandra-upgrade-from-1-0-6-to-1-1-X-tp7581197.html Sent from the cassandra-u...@incubator.apache.org mailing list archive at Nabble.com.

Re: Concerns about Cassandra upgrade from 1.0.6 to 1.1.X

On Wed, Jul 11, 2012 at 8:38 PM, Roshan codeva...@gmail.com wrote: Currently we are using Cassandra 1.0.6 in our production system but suffer with the CASSANDRA-3616 (it is already fixed in 1.0.7 version). We thought to upgrade the Cassandra to 1.1.X versions, to get it's new features, but

Re: Cassandra upgrade to 1.1.1 resulted in slow query issue

That does looks fishy. Would you mind opening a ticket on jira ( https://issues.apache.org/jira/browse/CASSANDRA) directly for that. It's easier for us to track it there. Thanks, Sylvain On Wed, Jun 13, 2012 at 8:05 PM, Ganza, Ivan iga...@globeandmail.comwrote: Greetings, ** ** We have

RE: Cassandra upgrade to 1.1.1 resulted in slow query issue

...@datastax.com] Sent: Thursday, June 14, 2012 8:20 AM To: user@cassandra.apache.org Cc: cassandra-u...@incubator.apache.org; Schlueter, Kevin Subject: Re: Cassandra upgrade to 1.1.1 resulted in slow query issue That does looks fishy. Would you mind opening a ticket on jira (https://issues.apache.org/jira

Cassandra upgrade to 1.1.1 resulted in slow query issue

Greetings, We have recently introduced Cassandra at the Globe and Mail here in Toronto, Canada. We are processing and storing the North American stock-market feed. We have found it to work very quickly and things have been looking very good. Recently we upgraded to version 1.1.1 and then we

Cassandra Upgrade from 0.8.1

Dear Guys, Thank you so much for your reply. Currently I have two Cassandra nodes running in ring. I have installed Cassandra on following location; /root/apache-cassandra-0.8.1 Now my questions are; 1. How we upgrade (Step by Step version like 0.8.1 to 0.8.5, then

RE: Cassandra Upgrade from 0.8.1

12:11 PM To: user@cassandra.apache.org Subject: Cassandra Upgrade from 0.8.1 Dear Guys, Thank you so much for your reply. Currently I have two Cassandra nodes running in ring. I have installed Cassandra on following location; /root/apache-cassandra-0.8.1 Now my questions are; 1. How

Re: Cassandra upgrade from 0.8.1 to 1.1.0

://www.datastax.com/docs/1.0/install/upgrading http://www.datastax.com/docs/1.1/install/upgrading Thanks. -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Cassandra-upgrade-from-0-8-1-to-1-1-0-tp7580198p7580210.html Sent from the cassandra-u

Re: Cassandra upgrade from 0.8.1 to 1.1.0

Hi Hope this will help to you. http://www.datastax.com/docs/1.0/install/upgrading http://www.datastax.com/docs/1.1/install/upgrading Thanks. -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Cassandra-upgrade-from-0-8-1-to-1-1-0

cassandra upgrade to 1.1 - migration problem

I recently upgraded from cassandra 1.0.10 to 1.1. Everything worked fine in one environment, but after I upgraded in another, I can't find my keyspace. When I run, e.g., cassandra-cli with 'use KeySpace;' It tells me that the keyspace doesn't exist. In the log I see this: ERROR

Re: cassandra upgrade to 1.1 - migration problem

Here's something new in the logs: ERROR 12:21:09,418 Exception in thread Thread[SSTableBatchOpen:2,5,main] java.lang.RuntimeException: Cannot open /var/lib/cassandra/data/system/Versions/system-Versions-hc-35 because partitioner does not match org.apache.cassandra.dht.ByteOrderedPartitioner

Re: cassandra upgrade to 1.1 - migration problem

cassandra.yaml on all nodes had ByteOrderedPartitioner with both the previous version and upgraded version. That being said, when I first started up cassandra after upgrading (with the updated .yaml, including ByteOrderedPartitioner) all nodes in the ring appeared to be up. But the load they

Re: cassandra upgrade to 1.1 - migration problem

The replication factor for a keyspace is stored in the system.schema_keyspaces column family. Since you can't view this with cli as the server won't start, the only way to look at it, that i know of is to use the sstable2json tool on the *.db file for that column family... So for instance

Re: cassandra upgrade to 1.1 - migration problem

On Tue, May 15, 2012 at 5:41 PM, Dave Brosius dbros...@mebigfatguy.comwrote: The replication factor for a keyspace is stored in the system.schema_keyspaces column family. Since you can't view this with cli as the server won't start, the only way to look at it, that i know of is to use the