Re: NTP Synchronization Setup Changes

Thanks for all the useful comments. On Thu, Mar 31, 2016 at 11:22 PM, Brice Dutheil wrote: > Hi another tip, make sure the OS doesn't come with pre-configured NTP > synchronisation services. We had a proper NTP setup, but we missed a > service that came with CentOS that

Re: NTP Synchronization Setup Changes

Hi another tip, make sure the OS doesn't come with pre-configured NTP synchronisation services. We had a proper NTP setup, but we missed a service that came with CentOS that synced to a low stratum NTP server. -- Brice On Thu, Mar 31, 2016 at 10:00 AM -0700, "Eric Evans"

Re: NTP Synchronization Setup Changes

On Wed, Mar 30, 2016 at 8:07 PM, Mukil Kesavan wrote: > Are there any issues if this causes a huge time correction on the cassandra > cluster? I know that NTP gradually corrects the time on all the servers. I > just wanted to understand if there were any corner cases

Re: NTP Synchronization Setup Changes

Hi Mickey, I would strongly suggest to setup a NTP server on your site - this is not really a big deal and with some tutorials on the net done quickly. Then configure your cassandra nodes (and all the rest if you like) to use your ntp instead of public ones. As I have learned the hard way -

NTP Synchronization Setup Changes

Hi, We run a 3 server cassandra cluster that is initially NTP synced to a single physical server over LAN. This server does not have connectivity to the internet for a few hours to sometimes even days. In this state we perform some schema operations and reads/writes with QUORUM consistency.