On Mon, Jun 20, 2011 at 5:54 PM, Jonathan Ellis wrote:
> We have great talks on indexing, CQL, time series data, Solandra,
> counters, and use cases from Netflix, Twitter, Urban Airship,
> Pantheon, and the Dachis group. Details on the "Speakers" tab of
> http://www.datastax.com/events/cassandras
Registration for this year's Cassandra SF so far is double that of
last year. Even though we're taking over the entire Mission Bay
Conference Center, this event will sell out. Details and RSVP are at:
http://www.datastax.com/events/cassandrasf2011
We're offering a 20% discount to Cassandra SF for
If anyone is interested, it was an issue of me using import instead of rr
(which only loads records, which, apparently, import did not).
- Original Message -
From: "Konstantin Naryshkin"
To: client-...@cassandra.apache.org
Sent: Monday, June 20, 2011 2:28:05 AM
Subject: Re: Cassandra 0.8
Ok, I'm closing this vote because we've decided to re-roll for
https://issues.apache.org/jira/browse/CASSANDRA-2797
Repair is fairly moody so it feels worth making it a little happier.
I'll reroll the artifacts to include this in a bit. Stay tuned.
--
Sylvain
On Mon, Jun 20, 2011 at 6:35 PM, Jon
Sorry, this is incorrect. The right answer is, "it's normal to see
'newer version' messages when mixing versions, until the newer node
realizes via gossip what version the old node is on and adjusts its
messages accordingly."
On Mon, Jun 20, 2011 at 8:57 AM, Jonathan Ellis wrote:
> Yes, rolling
After discussion on #cassandra-dev, I amend my vote to -0.
On Mon, Jun 20, 2011 at 10:29, Gary Dusbabek wrote:
> On Mon, Jun 20, 2011 at 10:12, Sylvain Lebresne wrote:
>> Yes, there has been a change of the messaging server version
>> between 0.8.0 and 0.8.1.
>>
>
> Do we hate our users or somet
On Mon, Jun 20, 2011 at 10:12, Sylvain Lebresne wrote:
> Yes, there has been a change of the messaging server version
> between 0.8.0 and 0.8.1.
>
Do we hate our users or something? This is a bad idea.
The whole idea behind CASSANDRA-1015 was that we would reserve changes
like this to major ver
Yes, there has been a change of the messaging server version
between 0.8.0 and 0.8.1.
--
Sylvain
On Mon, Jun 20, 2011 at 5:10 PM, Peter Schuller
wrote:
>> If things are working properly, he shouldn't see any of these messages
>> on a minor version upgrade because the version number should remain
> If things are working properly, he shouldn't see any of these messages
> on a minor version upgrade because the version number should remain
> constant. The message version should only change on major releases
> (if necessary).
>
> It could be that the existing cluster was built with non-release
On Mon, Jun 20, 2011 at 09:45, Sylvain Lebresne wrote:
> On Mon, Jun 20, 2011 at 1:58 PM, Shotaro Kamio wrote:
>> Hi,
>>
>> NEWS.txt claims that rolling upgrade works.
>> Upgrading
>> -
>> - 0.8.1 is backwards compatible with 0.8, upgrade can be achieved by a
>> simpl
On Mon, Jun 20, 2011 at 1:58 PM, Shotaro Kamio wrote:
> Hi,
>
> NEWS.txt claims that rolling upgrade works.
> Upgrading
> -
> - 0.8.1 is backwards compatible with 0.8, upgrade can be achieved by a
> simple rolling restart.
> --
>
> However, we got following mess
Yes, rolling upgrades are supported but streaming (repair, bootstrap,
move) is only supported when everyone is on the same version. (Same
was true for 0.7 -> 0.8.0)
On Mon, Jun 20, 2011 at 6:58 AM, Shotaro Kamio wrote:
> Hi,
>
> NEWS.txt claims that rolling upgrade works.
> Upgrading
> ---
Hi,
NEWS.txt claims that rolling upgrade works.
Upgrading
-
- 0.8.1 is backwards compatible with 0.8, upgrade can be achieved by a
simple rolling restart.
--
However, we got following messages when rolling upgrade from 0.8.0
based binary to 0.8 branch bina
13 matches
Mail list logo
