Hi there,
use case:
- Heavy write app, few reads.
- Lots of updates of rows / columns.
- Current performance is fine, for both writes and reads..
- Currently using SizedCompactionStrategy
We're trying to limit the amount of storage used during compaction. Should
we switch to
I upgraded a 2 node cluster with RF = 2 from 1.0.9 to 2.0.11. I did
rolling upgrades and upgradesstables after each upgrade. We then moved our
data to new hardware by shutting down each node, moving data to new
machine, and starting up with auto_bootstrap = false.
When all was done I ran a
at 11:15 AM, Robert Coli rc...@eventbrite.com wrote:
On Thu, Nov 20, 2014 at 8:36 AM, Stephane Legay sle...@looplogic.com
wrote:
I upgraded a 2 node cluster with RF = 2 from 1.0.9 to 2.0.11. I did
rolling upgrades and upgradesstables after each upgrade.
To be clear, did you go through 1.1
Here's the situation. We're running a 2-node cluster on EC2 (v 0.8.6). Each
node writes data to a mounted EBS volume mounted on /mnt2.
On Dec. 9th, for some reason both instances were rebooted (not sure yet
what triggered the reboot). But the EBS volumes were not added to
/etc/fstab, and didn't
That's good to know, thanks. I'm looking through my inbox but can't find
the notification you're referring to.
Oh well. Looks like we'll survive the day. That wasn't much fun at all.
On Mon, Dec 12, 2011 at 4:50 PM, Michael Shuler mich...@pbandjelly.orgwrote:
On 12/12/2011 12:53 PM, Stephane
Ok, will look into it, thx for the heads up.
Sent from a mobile device, please forgive typos.
On Aug 21, 2011 6:45 PM, Yan Chunlu springri...@gmail.com wrote:
I was aware of the deleted items might be come back alive without proper
node repair.
how about modified items, for example
Do you have anything to report on this? We're considering a move to Azure,
but Cassandra is the big unknown here.
I guess we could spawn some VM role instances and snapshot them regularly,
but if anyone's actually tried it, that would save us quite a bit of time.
Thanks!
On Wed, Mar 23, 2011 at
