On Tue, Dec 17, 2013 at 1:46 PM, Joel Segerlind wrote:
> Thanks for the info. However, wouldn't this also affect nodetool -pr (although
> not as much), which I ran on the same node the other day in about 35 min?
> I cannot understand how it can take 35 min for the primary range, and 25 h
> for a
On 17 December 2013 20:56, Robert Coli wrote:
> On Tue, Dec 17, 2013 at 11:46 AM, Joel Segerlind wrote:
>
>> Decommission streams a nodes key to the new node responsible for the
>>> range, why would a repair be required beforehand?
>>>
>>
>> I wondered the same thing, but I thought that the one
On Tue, Dec 17, 2013 at 11:46 AM, Joel Segerlind wrote:
> Decommission streams a nodes key to the new node responsible for the
>> range, why would a repair be required beforehand?
>>
>
> I wondered the same thing, but I thought that the one writing that ought
> to know way better than me.
>
Not
On 17 December 2013 20:40, Robert Coli wrote:
> On Tue, Dec 17, 2013 at 8:00 AM, Joel Segerlind wrote:
>
>> Hi,
>>
>> I'm trying to decommission a node from a six node Cassandra 2.0.3
>> cluster, following the instructions at
>> http://www.datastax.com/documentation/cassandra/2.0/webhelp/index.h
On Tue, Dec 17, 2013 at 8:00 AM, Joel Segerlind wrote:
> Hi,
>
> I'm trying to decommission a node from a six node Cassandra 2.0.3 cluster,
> following the instructions at
> http://www.datastax.com/documentation/cassandra/2.0/webhelp/index.html#cassandra/operations/ops_remove_node_t.html
>
...
Hi,
I'm trying to decommission a node from a six node Cassandra 2.0.3 cluster,
following the instructions at
http://www.datastax.com/documentation/cassandra/2.0/webhelp/index.html#cassandra/operations/ops_remove_node_t.html.
The node has just short of 11GB data in one keyspace (RF=3), and the repa
