Agree.
Just happy to see people upgrade to something 1.X
A
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 31/05/2012, at 8:24 AM, Rob Coli wrote:
> On Tue, May 29, 2012 at 10:29 PM, Pierre Chalamet wrote:
>> You'd better use version 1.0.9 (using
On Tue, May 29, 2012 at 10:29 PM, Pierre Chalamet wrote:
> You'd better use version 1.0.9 (using this one in production) or 1.0.10.
>
> 1.1 is still a bit young to be ready for prod unfortunately.
OP described himself as "experimenting" which I inferred to mean
not-production. I agree with others
prod unfortunately.
>
>
> --Original Message--
> From: Rob Coli
> To: user@cassandra.apache.org
> To: osish...@gmail.com
> ReplyTo: user@cassandra.apache.org
> Subject: Re: commitlog_sync_batch_window_in_ms change in 0.7
> Sent: May 30, 2012 03:12
>
> On Mon, May 2
t: Re: commitlog_sync_batch_window_in_ms change in 0.7
Sent: May 30, 2012 03:12
On Mon, May 28, 2012 at 6:53 AM, osishkin osishkin wrote:
> I'm experimenting with Cassandra 0.7 for some time now.
I feel obligated to recommend that you upgrade to Cassandra 1.1.
Cassandra 0.7 is better than 0.6, but I def
also nodetool disablegossip to stop other nodes sending requests to the one you
are about to shut down.
> I can shut down my cluster, but I don't want to have the nodes ignore
> it due to some schema misoconfiguration etc when I get it up again.
if you do a rolling restart the *cluster* will not
On Mon, May 28, 2012 at 6:53 AM, osishkin osishkin wrote:
> I'm experimenting with Cassandra 0.7 for some time now.
I feel obligated to recommend that you upgrade to Cassandra 1.1.
Cassandra 0.7 is better than 0.6, but I definitely still wouldn't be
"experimenting" with this old version in 2012.
Hi,
Using nodetool for each node one by one:
1. disablethrift
2. drain
3. Shutdown your daemon
4. Modify the config
5. Restart the node
You won't lose the data on your nodes - clients might see a node down, it is
usually not a problem if your c* client is smart enough. You also won't lose
updat
