On Mon, Jan 20, 2014 at 3:22 AM, Cyril Scetbon cyril.scet...@free.frwrote:
The only thing I'm worrying about is that I met a situation where I had a
lot of flushes on some nodes. You can find one of my system logs at
http://pastebin.com/YZKUQLXz. I'm not sure as I didn't let it run for
more
Hi made some tests which succeed
--
Cyril SCETBON
On 19 Jan 2014, at 01:14, Cyril Scetbon cyril.scet...@free.fr wrote:
So 1.2.2 and 1.2.13 have different file versions (ib vs ic)
We'll test if repairs are impacted by this change
Thanks
Cyril Scetbon
Le 17 janv. 2014 à 05:07, Aaron
(Forget my last mail)
Hi made some tests which succeed with all our operations (repair, add/remove
nodes ...). The only thing I'm worrying about is that I met a situation where I
had a lot of flushes on some nodes. You can find one of my system logs at
http://pastebin.com/YZKUQLXz. I'm not
So 1.2.2 and 1.2.13 have different file versions (ib vs ic)
We'll test if repairs are impacted by this change
Thanks
Cyril Scetbon
Le 17 janv. 2014 à 05:07, Aaron Morton aa...@thelastpickle.com a écrit :
Can you confirm that, cause we'll add a new DC with version 1.2.13
(read-only) and
Can you confirm that, cause we'll add a new DC with version 1.2.13
(read-only) and we'll upgarde other DCs to 1.2.13 weeks later. We made some
tests and didn't notice anything. But we didn't test a node failure
Depending on the other version you may not be able to run repair. All nodes
have
Hi,
Can you confirm that, cause we'll add a new DC with version 1.2.13 (read-only)
and we'll upgarde other DCs to 1.2.13 weeks later. We made some tests and
didn't notice anything. But we didn't test a node failure
thanks
--
Cyril SCETBON
On 08 Jan 2014, at 19:24, Robert Coli
On Mon, Jan 13, 2014 at 3:38 AM, Cyril Scetbon cyril.scet...@free.frwrote:
Can you confirm that, cause we'll add a new DC with version 1.2.13
(read-only) and we'll upgarde other DCs to 1.2.13 weeks later. We made some
tests and didn't notice anything. But we didn't test a node failure
In
Thank you both for the answers!
Jiri Horky
On 01/10/2014 02:52 AM, Aaron Morton wrote:
We avoid mixing versions for a long time, but we always upgrade one
node and check the application is happy before proceeding. e.g. wait
for 30 minutes before upgrading the others.
If you snapshot before
We avoid mixing versions for a long time, but we always upgrade one node and
check the application is happy before proceeding. e.g. wait for 30 minutes
before upgrading the others.
If you snapshot before upgrading, and have to roll back after 30 minutes you
can roll back to the snapshot and
Hi all,
I would appreciate an advice whether is a good idea to upgrade from
cassandra 1.2.3 to 1.2.13 and how to best proceed. The particular
cluster consists of 3 nodes (each one in a different DC having 1
replica) with a relativelly low traffic and 10GB load per node.
I am specifically
On Wed, Jan 8, 2014 at 1:17 AM, Jiri Horky ho...@avast.com wrote:
I am specifically interested whether is possible to upgrade just one
node and keep it running like that for some time, i.e. if the gossip
protocol is compatible in both directions. We are a bit afraid to
upgrade all nodes to
11 matches
Mail list logo
