Hi, I would say that i agree with Jon, Jeff and Alain at the same time ;-)
Basically you should be very comfortable to do it for conf, cassandra version or Os update but not because if you not do it your cluster starts suffering from performance issues or something like that. If so, you should investigate the issues but it's not normal. Cheers, Jérémy Le mer. 16 oct. 2019 à 17:34, Jon Haddad <j...@jonhaddad.com> a écrit : > I agree with Jeff here. Ideally you should be so comfortable with rolling > restarts that they become second nature. Cassandra is designed to handle > them and you should not be afraid to do them regularly. > > On Wed, Oct 16, 2019, 8:06 AM Jeff Jirsa <jji...@gmail.com> wrote: > >> >> Personally I encourage you to rolling restart from time to time, use it >> as an opportunity to upgrade kernels and JDKs and cassandra itself and just >> generally make sure things are healthy and working how you expect >> >> If you see latencies jump or timeouts when you’re bouncing, that’s a >> warning and you know you need to address it - doing this in advance gives >> you a chance to do it while the bounce is optional and can be paused. If >> you wait for a switch to fail or AWS AZ to crash, you may have problems >> lurking you don’t know about until it’s too late. >> >> - Jeff >> >> > On Oct 16, 2019, at 12:56 AM, Marco Gasparini < >> marco.gaspar...@competitoor.com> wrote: >> > >> > >> > hi all, >> > >> > I was wondering if it is recommended to perform a rolling restart of >> the cluster once in a while. >> > Is it a good practice or necessary? how often? >> > >> > Thanks >> > Marco >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org >> For additional commands, e-mail: user-h...@cassandra.apache.org >> >> -- Jérémy
