Re: On 0.6.6 to 0.7.3 migration, DC-aware traffic and minimising data transfer

2011-03-18 Thread Jonathan Ellis
than Ellis [mailto:jbel...@gmail.com] > Sent: Wednesday, March 16, 2011 1:59 PM > To: user@cassandra.apache.org > Cc: Jedd Rashbrooke > Subject: Re: On 0.6.6 to 0.7.3 migration, DC-aware traffic and minimising > data transfer > > That should work then, assuming SimpleStrategy/R

RE: On 0.6.6 to 0.7.3 migration, DC-aware traffic and minimising data transfer

2011-03-18 Thread Jeremiah Jordan
: Wednesday, March 16, 2011 1:59 PM To: user@cassandra.apache.org Cc: Jedd Rashbrooke Subject: Re: On 0.6.6 to 0.7.3 migration, DC-aware traffic and minimising data transfer That should work then, assuming SimpleStrategy/RackUnawareStrategy. Otherwise figuring out which machines share which data gets

Re: On 0.6.6 to 0.7.3 migration, DC-aware traffic and minimising data transfer

2011-03-16 Thread Jonathan Ellis
That should work then, assuming SimpleStrategy/RackUnawareStrategy. Otherwise figuring out which machines share which data gets complicated. Note that if you have room on the machines, it's going to be faster to copy the entire data set to each machine and run cleanup, than to have repair fix 3 of

Re: On 0.6.6 to 0.7.3 migration, DC-aware traffic and minimising data transfer

2011-03-14 Thread David Boxenhorn
How do you write to two versions of Cassandra from the same client? Two versions of Hector? On Mon, Mar 14, 2011 at 6:46 PM, Robert Coli wrote: > On Mon, Mar 14, 2011 at 8:39 AM, Jedd Rashbrooke > wrote: > > But more importantly for us it would mean we'd have just the > > one major outage, ra

Re: On 0.6.6 to 0.7.3 migration, DC-aware traffic and minimising data transfer

2011-03-14 Thread Robert Coli
On Mon, Mar 14, 2011 at 8:39 AM, Jedd Rashbrooke wrote: >  But more importantly for us it would mean we'd have just the >  one major outage, rather than two (relocation and 0.6 -> 0.7) Take zero major outages instead? :D a) Set up new cluster on new version. b) Fork application writes, so all wr

Re: On 0.6.6 to 0.7.3 migration, DC-aware traffic and minimising data transfer

2011-03-14 Thread Jedd Rashbrooke
Jonathon, thank you for your answers here. To explain this bit ... On 11 March 2011 20:46, Jonathan Ellis wrote: > On Thu, Mar 10, 2011 at 6:06 AM, Jedd Rashbrooke wrote: >>  Copying a cluster between AWS DC's: >>  We have ~ 150-250GB per node, with a Replication Factor of 4. >>  I ack that 0

Re: On 0.6.6 to 0.7.3 migration, DC-aware traffic and minimising data transfer

2011-03-14 Thread Chris Burroughs
On 03/11/2011 03:46 PM, Jonathan Ellis wrote: > Repairs is not yet WAN-optimized but is still cheap if your replicas > are close to consistent since only merkle trees + inconsistent ranges > are sent over the network. > What is the ticket number for WAN optimized repair?

Re: On 0.6.6 to 0.7.3 migration, DC-aware traffic and minimising data transfer

2011-03-11 Thread Jonathan Ellis
On Thu, Mar 10, 2011 at 6:06 AM, Jedd Rashbrooke wrote: >  My question is whether it's considered safer to upgrade via 0.6.12 >  to 0.7, or if a direct 0.6.6 -> 0.7 upgrade is safe enough? You don't need latest 0.6 before upgrading. >  Copying a cluster between AWS DC's: >  We have ~ 150-250GB p

On 0.6.6 to 0.7.3 migration, DC-aware traffic and minimising data transfer

2011-03-10 Thread Jedd Rashbrooke
Howdi, Assortment of questions relating to an upgrade combined with a possible migration between Data Centers (or perhaps a multi-DC redesign). Apologies if some of these have been asked before - I have kept half an eye on the list in recent times but haven't seen anything covering these pa