ry.
>
>
> On Fri, Feb 25, 2011 at 04:24, Daniel Josefsson wrote:
> > We experienced the java.lang.NegativeArraySizeException when upgrading to
> > 0.7.2 in staging. The proposed solution (running compaction) seems to have
> > solved this. However it took a lot of
We experienced the java.lang.NegativeArraySizeException when upgrading to
0.7.2 in staging. The proposed solution (running compaction) seems to have
solved this. However it took a lot of time to run.
Is it safe to invoke a major compaction on all of the machines concurrently?
I can't see a reason
r.runTask(ThreadPoolExecutor.java:886)
> > > at
> > > java.util.concurrent.ThreadPoolExecutor
> > $Worker.run(ThreadPoolExecutor.java:908)
> > > at java.lang.Thread.run(Thread.java:662)
> > > Caused by: java.io.IOException: Unable to rename cache to
> > > F:\Cassandra\7.2\saved
topic because we're currently thinking about the same
> thing - how to upgrade to 0.7 without any interruption.
>
> Dave
>
> On 21 January 2011 09:20, Daniel Josefsson <
> jid...@gmail.com> wrote:
>
>> No, what I'm thinking of is having two clusters (0.6 and
ode protocol prohibit this. The nodes will
> probable see each either via gossip, but the way the messages define their
> purpose (their verb handler) has been changed.
>
> Out of interest which is more painful, stopping the cluster and upgrading
> it or upgrading your client code?
&g
In our case our replication factor is more than half the number of nodes in
the cluster.
Would it be possible to do the following:
- Upgrade half of them
- Change Thrift Port and inter-server port (is this the storage_port?)
- Start them up
- Upgrade clients one by one
- Upgrade th
Hi,
I've been looking around for how to upgrade from 0.6 to 0.7, and it looks
like you need to shut down the whole cluster, plus upgrade the clients at
the same time.
Our live cassandra instances are currently running 0.6.4 with an ever
growing database and need the new TTL feature available in 0
