This is not the case; I built and deployed the latest code from the 2.1.x
branch in Github and the issue still exists.
- Mike
From: Jeff Jirsa mailto:jeff.ji...@crowdstrike.com>>
Reply-To: Cassandra List
mailto:user@cassandra.apache.org>>
Date: Wednesday, July 29, 2015 at 12:07 PM
To: Cassandra
I figured out the issue. Mainly the setting is related to
commitlog_segment_size_in_mb
and the sync I am currently have across three other remote site.
thanks,
Noah
On Thu, Jul 30, 2015 at 1:05 PM, noah chanmala wrote:
> All,
>
> Would you please point me to location where I can adjust/reconf
>
>
>
> Why are you using 2.2? In general Cassandra, like most software, can lack
> stability near the bleeding edge.
>
>
I'll be honest, I didn't realise I was using the bleeding edge! I had begun
playing around with dsc21 (from the datastax apt repo) but when that failed
to install correctly due
