You are upgrading to 2.0 in Prod? What is the urgency?
On Sun, Sep 22, 2013 at 7:02 PM, Shashilpi Krishan <
shashilpi.kris...@wizecommerce.com> wrote:
> Hi Everyone.
>
>
>
> We had a Cassandra cluster (running with v1.0.7) spread across 3 data
> centers with each data center having 16 nodes. We
Hi Everyone.
We had a Cassandra cluster (running with v1.0.7) spread across 3 data centers
with each data center having 16 nodes. We started upgrading that to 2.0 but
realized that we can't go directly to 2.0 due to read failures, hence to avoid
down time we have to go from 1.0 --> 1.1 --> 1.2
Having commit log and data directory under one SSD works well. Though it
depends a lot on the use case. I would measure the Disk utilization and see
whether it can be on one. For most of the cases, it will work fine on one
SSD.
On Sun, Sep 22, 2013 at 4:02 PM, Shahryar Sedghi wrote:
> This my f
This my first SSD experience. With normal disks we separate commit log
from data. We have 2 SSDs dedicated to Cassandra I was wondering if we
gain a better performance if we put commit log in one and data in
another, or just use raid 0 to have both SSDs combined.
Thanks in Advance
Shahryar
Hello
I have resolved the issue by recreating tables and recalculating them ( i
use counter columns for summary , so live data allows me to recalculate it
).
As for upgrading i walked over issues list and found that issues either
where resolved in 0.8.3 , 0.8.4 or opened till now ( my version is 0
