As long as your nodes are syncing time using the same method, that should be good. Don't mix daemons, however, since they may sync from different sources. Whether you use ntpd, openntp, ntpsec, chrony isn't really important, since they are all just background daemons to sync the system clock. There is nothing Cassandra-specific.
-- Kind regards, Michael On 03/08/2018 04:15 AM, Kyrylo Lebediev wrote: > Hi! > > Recently Amazon announced launch of Amazon Time Sync Service > (https://aws.amazon.com/blogs/aws/keeping-time-with-amazon-time-sync-service/) > and now it's AWS-recommended way for time sync on EC2 instances > (https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/set-time.html). > It's stated there that chrony is faster / more precise than ntpd. > > Nothing to say correct time sync configuration is very important for any > C* setup. > > Does anybody have positive experience using crony, Amazon Time Sync > Service with Cassandra and/or combination of them? > Any concerns regarding chrony + Amazon Time Sync Service + Cassandra? > Are there any chrony best-practices/custom settings for C* setups? > > Thanks, > Kyrill > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
