You can run removenode instead of decommission while it's down to avoid it being online / serving reads at all.
You can also start cassandra with ` start_native_transport : false ` to deter clients from connecting directly to it, though to be fair, that doesnt eliminate the possibility that it's used for reads. On Thu, Sep 19, 2019 at 10:20 AM Krishna PMV <[email protected]> wrote: > Hi, > I ran into a situation where a newly bootstrapped node in the cluster has > crashed (due to known issue) immediately after the bootstrap process and > it remained dead for about 8 hours. > Since the node is down for about 8 hours, its missing some data after I > start cassandra. My application with queries of consistency LOCAL_ONE > started failing as a result. Now, the node is in stopped state for about 12 > hours and I'm planning to decommission the node. (I know running repairs is > another option but it will take a while since data size is about 350G and > since it serves reads during repair process, I wanted to avoid this, if we > can). > > So, I wanted to know if the node serves read requests during decommission > process i.e., while leaving the cluster. > > Thanks! >
