incubator-cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Brown <>
Subject decommission and hints
Date Sat, 05 Jan 2013 06:20:37 GMT
Hi all,

Looks like decommissioning a node (nodetool decommission) will stream all
the non-system table data out to it's appropriate peers
(StorageService.unbootstrap()), but what should happen to hints? From
reading StorageService, it seems like nothing in particular forces them to
get replayed (which makes sense) or stashed onto another, live node.

The use case here is auto-scaling vnode clusters in ec2. In the normal
usage (that is, today in c* 1.1 running in the cloud), we never call
decommission as clusters always remain at a fixed, stable size. However,
when auto-scaling down a vnode cluster, I'd want to call decommission on
the node to leave the ring (and be terminated).

I'm worried about terminating a node and it's hints never getting played
before it disappears. Node repair, of course, would help on the
anti-entropy front, but wondering if there's value in streaming the hints
to a peer (in the same rack?).


-Jason Brown

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message