4 ms·
NTP works fine. This is a very minor risk. VMs on cloud providers are already preconfigured to use NTP with their own time servers so they are very reliable [1]
by manigandham 7y ago
NTP works fine. This is a very minor risk. VMs on cloud providers are already preconfigured to use NTP with their own time servers so they are very reliable [1][2] and you can always add your own monitoring [3]. Also CRDB is tested with clock-drift and you can read the jepsen report [4].
1. https://aws.amazon.com/blogs/aws/keeping-time-with-amazon-time-sync-service/ https://aws.amazon.com/blogs/aws/keeping-time-with-amazon-ti...
2. https://developers.google.com/time/ https://developers.google.com/time/
3. https://docs.datadoghq.com/integrations/ntp/ https://docs.datadoghq.com/integrations/ntp/
4. https://jepsen.io/analyses/cockroachdb-beta-20160829 https://jepsen.io/analyses/cockroachdb-beta-20160829
- Havoc 7y ago>NTP works fine. This is a very minor risk. Until it doesn't. Low probability large impact doesn't directly translate to minor risk imo
- craftinator 7y agoI'm terrified of meteors too!
- scottlocklin 7y agoGreat; so have you used CockroachDB in production? I bet you haven't!
- manigandham 7y agoYes, read my other comment at the top of this page.