Re: [Cassandra] Replacing a cassandra node with one of the same IP

2013-06-26 Thread aaron morton
 So are hints to a given UUID discarded after some period of time with
 that UUID not present in the cluster?
From memory they are TTL'd at the gc_grace_seconds for the CF.

Cheers

-
Aaron Morton
Freelance Cassandra Consultant
New Zealand

@aaronmorton
http://www.thelastpickle.com

On 26/06/2013, at 5:11 AM, Robert Coli rc...@eventbrite.com wrote:

 On Mon, Jun 24, 2013 at 8:53 PM, aaron morton aa...@thelastpickle.com wrote:
 so I am just wondering if this means the hinted handoffs are also updated 
 to reflect the new Cassandra node uuid.
 Without checking the code I would guess not.
 Because it would involve a potentially large read / write / delete to create 
 a new row with the same data. And Hinted Handoff is an optimisation.
 
 So are hints to a given UUID discarded after some period of time with
 that UUID not present in the cluster? Or might they need to be
 manually purged?
 
 =Rob



Re: [Cassandra] Replacing a cassandra node with one of the same IP

2013-06-25 Thread Robert Coli
On Mon, Jun 24, 2013 at 8:53 PM, aaron morton aa...@thelastpickle.com wrote:
 so I am just wondering if this means the hinted handoffs are also updated to 
 reflect the new Cassandra node uuid.
 Without checking the code I would guess not.
 Because it would involve a potentially large read / write / delete to create 
 a new row with the same data. And Hinted Handoff is an optimisation.

So are hints to a given UUID discarded after some period of time with
that UUID not present in the cluster? Or might they need to be
manually purged?

=Rob


Re: [Cassandra] Replacing a cassandra node with one of the same IP

2013-06-24 Thread aaron morton
 so I am just wondering if this means the hinted handoffs are also updated to 
 reflect the new Cassandra node uuid. 
Without checking the code I would guess not. 
Because it would involve a potentially large read / write / delete to create a 
new row with the same data. And Hinted Handoff is an optimisation. 

Cheers

-
Aaron Morton
Freelance Cassandra Consultant
New Zealand

@aaronmorton
http://www.thelastpickle.com

On 22/06/2013, at 9:52 AM, Mahony, Robin robin.mah...@netapp.com wrote:

 Please note that I am currently using version 1.2.2 of Cassandra.  Also we 
 are using virtual nodes.
  
 My question mainly stems from the fact that the nodes appear to be aware that 
 the node uuid changes for the IP (from reading the logs), so I am just 
 wondering if this means the hinted handoffs are also updated to reflect the 
 new Cassandra node uuid. If that was the case, I would not think a nodetool 
 cleanup would be necessary.
  
 - Forwarded Message -
 From: Robert Coli rc...@eventbrite.com
 To: user@cassandra.apache.org; Emalayan Vairavanathan svemala...@yahoo.com 
 Sent: Thursday, 20 June 2013 11:40 AM
 Subject: Re: [Cassandra] Replacing a cassandra node
 
 On Thu, Jun 20, 2013 at 10:40 AM, Emalayan Vairavanathan
 svemala...@yahoo.com wrote:
  In the case where replace a cassandra node (call it node A) with another one
  that has the exact same IP (ie. during a node failure), what exactly should
  we do?  Currently I understand that we should at least run nodetool
  repair.
 
 If you lost the data from the node, then what you want is replace_token.
 
 If you didn't lose the data from the node (and can tolerate stale
 reads until the repair completes) you want to start the node with
 auto_bootstrap set to false and then repair.
 
 =Rob



Re: [Cassandra] Replacing a cassandra node with one of the same IP

2013-06-21 Thread Mahony, Robin
Please note that I am currently using version 1.2.2 of Cassandra.  Also we are 
using virtual nodes.

My question mainly stems from the fact that the nodes appear to be aware that 
the node uuid changes for the IP (from reading the logs), so I am just 
wondering if this means the hinted handoffs are also updated to reflect the new 
Cassandra node uuid. If that was the case, I would not think a nodetool cleanup 
would be necessary.

- Forwarded Message -
From: Robert Coli rc...@eventbrite.commailto:rc...@eventbrite.com
To: user@cassandra.apache.orgmailto:user@cassandra.apache.org; Emalayan 
Vairavanathan svemala...@yahoo.commailto:svemala...@yahoo.com
Sent: Thursday, 20 June 2013 11:40 AM
Subject: Re: [Cassandra] Replacing a cassandra node

On Thu, Jun 20, 2013 at 10:40 AM, Emalayan Vairavanathan
svemala...@yahoo.commailto:svemala...@yahoo.com wrote:
 In the case where replace a cassandra node (call it node A) with another one
 that has the exact same IP (ie. during a node failure), what exactly should
 we do?  Currently I understand that we should at least run nodetool
 repair.

If you lost the data from the node, then what you want is replace_token.

If you didn't lose the data from the node (and can tolerate stale
reads until the repair completes) you want to start the node with
auto_bootstrap set to false and then repair.

=Rob