Well I guess I'm glad to know I didn't just miss something obvious. I
voted for the issue on Jira; I don't know if that's used to prioritize
features or not, but it can't hurt, right? =)
On Wed, Jun 26, 2013 at 3:03 PM, Robert Coli wrote:
> On Fri, Jun 21, 2013 at 5:25 AM, Eric Stevens wrote:
> 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.co
On Fri, Jun 21, 2013 at 5:25 AM, Eric Stevens wrote:
> Is there a way to replace a failed server using vnodes? I only had occasion
> to do this once, on a relatively small cluster. ...
> Of course that caused a bunch of key reassignments,
> so I'm sure it would be less work for the cluster if I
On Mon, Jun 24, 2013 at 8:53 PM, aaron morton 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 creat
id. If that was the case, I would not think a nodetool
> cleanup would be necessary.
>
> - Forwarded Message -
> From: Robert Coli
> To: user@cassandra.apache.org; Emalayan Vairavanathan
> Sent: Thursday, 20 June 2013 11:40 AM
> Subject: Re: [Cassandra] Replac
t;; Emalayan
Vairavanathan mailto: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
mailto:svemala...@yahoo.com>> wrote:
> In the case where replace a cassandra node (call
Is there a way to replace a failed server using vnodes? I only had
occasion to do this once, on a relatively small cluster. At the time I
just needed to get the new server online and wasn't concerned about the
performance implications, so I just removed the failed server from the
cluster and boot
On Thu, Jun 20, 2013 at 10:40 AM, Emalayan Vairavanathan
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
> repa
Hi All,
I have a question.
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". I noticed that the cassandra system
