On Fri, Mar 27, 2015 at 4:01 AM, Jason Wee wrote:
> Rob, the cluster now upgraded to cassandra 1.0.12 (default hd version,
> in Descriptor.java) and I ensure all sstables in current cluster are
> hd version before upgrade to cassandra 1.1. I have also checked in
> cassandra 1.1.12 , the sstable i
On Fri, Mar 27, 2015 at 7:20 AM, Jonathan Haddad wrote:
> Running upgrade is a noop if the tables don't need to be upgraded. I
> consider the cost of this to be less than the cost of missing an upgrade.
Oh, right! This optimization was added, which means I totally and
completely agree with you.
Running upgrade is a noop if the tables don't need to be upgraded. I
consider the cost of this to be less than the cost of missing an upgrade.
On Thu, Mar 26, 2015 at 4:23 PM Robert Coli wrote:
> On Wed, Mar 25, 2015 at 7:16 PM, Jonathan Haddad
> wrote:
>
>> There's no downside to running upgrad
Rob, the cluster now upgraded to cassandra 1.0.12 (default hd version,
in Descriptor.java) and I ensure all sstables in current cluster are
hd version before upgrade to cassandra 1.1. I have also checked in
cassandra 1.1.12 , the sstable is version hf version. so i guess,
nodetool upgradesstables i
On Wed, Mar 25, 2015 at 7:16 PM, Jonathan Haddad wrote:
> There's no downside to running upgradesstables. I recommend always doing
> it on upgrade just to be safe.
For the record and just my opinion : I recommend against paying this fixed
cost when you don't need to.
It is basically trivial to
5, 2015 10:59 AM
> > To: user@cassandra.apache.org
> > Subject: Re: upgrade from 1.0.12 to 1.1.12
> >
> > hmm... okay.
> >
> > one more question
> > https://github.com/apache/cassandra/blob/cassandra-1.1.12/NEWS.txt I
> upgraded directly to 1.1.12 , do I
-
> From: Jason Wee [mailto:peich...@gmail.com]
> Sent: Wednesday, March 25, 2015 10:59 AM
> To: user@cassandra.apache.org
> Subject: Re: upgrade from 1.0.12 to 1.1.12
>
> hmm... okay.
>
> one more question
> https://github.com/apache/cassandra/blob/cassandra-1.1.12/N
(repairs and bootstraps).
Sean Durity – Cassandra Admin, Big Data Team
To engage the team, create a request
-Original Message-
From: Jason Wee [mailto:peich...@gmail.com]
Sent: Wednesday, March 25, 2015 10:59 AM
To: user@cassandra.apache.org
Subject: Re: upgrade from 1.0.12 to 1.1.12
hmm... okay.
one more question
https://github.com/apache/cassandra/blob/cassandra-1.1.12/NEWS.txt I
upgraded directly to 1.1.12 , do I need to run nodetool
upgradesstables as stipulated in version 1.1.3 ?
jason
On Wed, Mar 25, 2015 at 1:04 AM, Jonathan Haddad wrote:
> Streaming is repair, addi
Streaming is repair, adding & removing nodes. In general it's a bad idea
to do any streaming op when you've got an upgrade in progress.
On Tue, Mar 24, 2015 at 3:14 AM Jason Wee wrote:
> Hello,
>
> Reading this documentation http://www.datastax.com/docs/
> 1.1/install/upgrading
>
> If you are u
Hello,
Reading this documentation http://www.datastax.com/docs/1.1/install/upgrading
If you are upgrading to Cassandra 1.1.9 from a version earlier than
1.1.7, all nodes must be upgraded before any streaming can take place.
Until you upgrade all nodes, you cannot add version 1.1.7 nodes or
later
11 matches
Mail list logo