Actually I had modified the source code (to put a patch for cassandra
to work across EC2 regions). That patch seems to be causing issue with
'nodetool repair'
When I run without the patch (and within an ec2 region), the repair
completes within reasonable time.
On Tue, Mar 22, 2011 at 12:40 PM, Rob
On Tue, Mar 22, 2011 at 8:53 AM, A J wrote:
> 0.7.4
>
> On Tue, Mar 22, 2011 at 11:49 AM, Robert Coli wrote:
>> On Mon, Mar 21, 2011 at 8:33 PM, A J wrote:
>>> I am trying to estimate the time it will take to rebuild a node. After
>>> loading reasonable data,
http://issues.apache.org/jira/brows
0.7.4
On Tue, Mar 22, 2011 at 11:49 AM, Robert Coli wrote:
> On Mon, Mar 21, 2011 at 8:33 PM, A J wrote:
>> I am trying to estimate the time it will take to rebuild a node. After
>> loading reasonable data,
>> ...
>> For some reason, the repair command runs forever. I just have 3G of
>> data per
On Mon, Mar 21, 2011 at 8:33 PM, A J wrote:
> I am trying to estimate the time it will take to rebuild a node. After
> loading reasonable data,
> ...
> For some reason, the repair command runs forever. I just have 3G of
> data per node but still the repair is running for more than an hour !
What
Are you monitoring the progress http://wiki.apache.org/cassandra/Streaming ?
or with nodetool netstats
Aaron
On 22 Mar 2011, at 16:33, A J wrote:
> I am trying to estimate the time it will take to rebuild a node. After
> loading reasonable data, I brought down a node and manually removed
> all
I am trying to estimate the time it will take to rebuild a node. After
loading reasonable data, I brought down a node and manually removed
all its datafiles for a given keyspace (Keyspace1)
I then restarted the node and got i back in the ring. At this point, I
wish to run nodetool repair (bin/nodet
