am guessing a lot here, but I would check if auto_bootstrap is enabled. It is
by default.
When a new node joins reads are not directed to it until it is marked as "UP"
(writes are sent to it as it is joining). So reads should continue to go to the
original UP node.
Sounds like it's all runnin
On Thu, Mar 1, 2012 at 9:33 AM, aaron morton wrote:
> What RF were you using and had you been running repair regularly ?
>
>
RF 1 *sigh*. Waiting until I have more/better resources to use RF > 1.
Hopefully soon.
In the mean time... Oddly (to me), when I removed the most recently added
node, all
What RF were you using and had you been running repair regularly ?
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 1/03/2012, at 5:51 AM, Casey Deccio wrote:
> On Wed, Feb 29, 2012 at 5:29 AM, Casey Deccio wrote:
> On Wed, Feb 29, 2012 at
On Wed, Feb 29, 2012 at 5:29 AM, Casey Deccio wrote:
> On Wed, Feb 29, 2012 at 5:25 AM, Casey Deccio wrote:
>
>> I recently had to do some shuffling with one of my cassandra nodes
>> because it was running out of disk space. I did a few things in the
>> process, and I'm not sure in the end whic
On Wed, Feb 29, 2012 at 5:25 AM, Casey Deccio wrote:
> I recently had to do some shuffling with one of my cassandra nodes because
> it was running out of disk space. I did a few things in the process, and
> I'm not sure in the end which caused my problem. First I added a second
> file path to t
I recently had to do some shuffling with one of my cassandra nodes because
it was running out of disk space. I did a few things in the process, and
I'm not sure in the end which caused my problem. First I added a second
file path to the data directory in cassandra.yaml. Things still worked
fine
