On Tue, Jun 30, 2015 at 11:59 AM, Dan Kinder <dkin...@turnitin.com> wrote:
> Is this unusual or the same thing others see? Is `nodetool drain` really > supposed to wait until all memtables are flushed and commitlogs are deleted > before it returns? > "nodetool drain" *should* work the way you suggest - if one runs it before shutdown and waits for the "DRAINED" message in the log, one should get no commitlog replay on start. In practice, this has historically not-worked at various times. https://issues.apache.org/jira/browse/CASSANDRA-4446 https://issues.apache.org/jira/browse/CASSANDRA-5911 / https://issues.apache.org/jira/browse/CASSANDRA-3578 (marked fixed in 2.1 beta) It's pretty harmless to over-replay in most cases, one is most-hosed if one is using counters. But if you can repro in 2.1.7 by restarting at any time after the DRAINED message, you should file an issue on issues.apache.org and reply here to let the list know the URL for it. =Rob
