I created an issue for this: https://issues.apache.org/jira/browse/CASSANDRA-8801
On Thu, Feb 12, 2015 at 10:18 AM, Robert Coli <rc...@eventbrite.com> wrote: > On Thu, Feb 12, 2015 at 7:04 AM, Eric Stevens <migh...@gmail.com> wrote: > >> IMO, especially with the threat to unrecoverable consistency violations, >> this should be a critical bug. >> > > You should file a JIRA, and let the list know what it is? :D > > I was never sure if it was just me being unreasonably literal to presume > that decommission made the node forget its prior state, if I'm honest? It > is nice to hear from other operators that this matches their expectations. > But yes, the current behavior seems to have risks that "forgetting" > doesn't, and I don't understand what benefits (if any) it has. > > As a brief aside, this is Yet Another Reason why you probably don't ever > want a Cassandra node to automatically start on boot, or restart. If you > don't know its configuration, it could join a cluster, which might be > Meaningfully Bad in some circumstances. > > =Rob >
