Hi Jerome, The node being drained stops listening to requests but the other nodes being coordinators for given requests will store hints for that downed node for a configured period of time (max_hint_window_in_ms is 3 hours by default). If the downed node is back online in this time window it will receive hints from other nodes in the cluster and eventually catch up. What is your typical maintenance downtime?
Regards, Matija On Fri, Sep 2, 2016 at 10:53 PM, jerome <jeromefroel...@hotmail.com> wrote: > Hello, > > > As part of routine maintenance for our cluster, my colleagues and I > will run a nodetool drain before stopping a Cassandra node, performing > maintenance, and bringing it back up. We run maintenance as a cron-job with > a lock stored in a different cluster to ensure only node is ever down at a > time. We would like to make sure the node has replayed all its hints before > bringing it down to minimize the potential window in which users might read > out-of-date data (we read at a consistency level of ONE). Is it possible to > replay hints after performing a nodetool drain? The documentation leads me > to believe its not since Cassandra will stop listening for connections from > other nodes, but I was unable to find anything definitive either way. If a > node won't replay hints after a nodetool drain, is there perhaps another > way to tell Cassandra to stop listening for client connections but continue > to replay hints to other nodes. > > > Thanks, > > Jerome >
