Yes, I meant RF: 2,2,1. We have the following in our network topo config: # cass08: us-west-1c
private.ip=DC-A:1 public.ip=DC-A:1 # cass09: us-west-1b private.ip=DC-A:2 public.ip=DC-A:2 # cass10: Linode-Fremont-CA public.ip=DC-C:1 # cass11: us-west-2c private.ip=DC-B:1 public.ip=DC-B:1 # cass12: us-west-2b private.ip=DC-B:2 public.ip=DC-B:2 We're figuring out the upgrade right now. In general, what is the expected upgrade time per node for ~50GB (on each node)? Thanks arup On Wed, Jun 4, 2014 at 11:08 AM, Robert Coli <[email protected]> wrote: > On Wed, Jun 4, 2014 at 12:12 AM, Arup Chakrabarti <[email protected]> > wrote: > >> Size: 5 nodes (2 in AWS US-West-1, 2 in AWS US-West-2, 1 in Linode >> Fremont) >> Replication Factor: 5 >> > > You're operating with a single-DC strategy across multiple data centers? > If so, I'm surprised you get sane latency ever. > > (Or do you mean RF : 2,2,1?) > > I agree with others that problems which can cause cluster wide outages > exist in Gossip in the version of Cassandra you are running. > > As a general piece of feedback, I suggest an upgrade, first to 1.1 HEAD, > then 1.2.16. > > =Rob > >
