2.1.16 is old, but it's not as old as 2.1.6, which is what you originally put, and would be much more concerning.
It is true, however, that 'removenode' involves streaming data, and streaming data can be GC intensive (especially with compression enabled), which means if your cluster is on the edge of health you may cause it to teeter over the edge during streaming, causing nodes to flap (the DOWN messages in the logs). That doesn't really explain the schema change, though - how confident are you that the schema was properly in sync prior to the removenode? - Jeff On 2017-06-29 09:49 (-0700), Jai Bheemsen Rao Dhanwada <jaibheem...@gmail.com> wrote: > Hello Jeff, > > Yes 2.1.16 is old version, and we are planning to upgrade in few months. > > Only the gossiper info is logged stating that it marked several nodes down > and nothing else. > > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org For additional commands, e-mail: user-h...@cassandra.apache.org
