Re: ntpd clock sync

2016-03-12 Thread Spencer Brown
but what I'm saying is that every second will still hit. It's just that that second will only last for 0.8s. So to the code above the OS and even the shell level system calls, there is no difference. The difference is very lo level - interrupts come in every micro-second or so from the CPU and t

Re: ntpd clock sync

2016-03-12 Thread John Wong
I believe K is asking whether he can sync up the clock now because he's concerned about losing data, as 30-40 seconds is pretty bad. On Sat, Mar 12, 2016 at 8:57 AM, Spencer Brown wrote: > NTP gradually speeds or slows the clock to arrive at actual time. So the > clock still hits every second b

Re: ntpd clock sync

2016-03-12 Thread Spencer Brown
NTP gradually speeds or slows the clock to arrive at actual time. So the clock still hits every second but 1s may really be 0.8s or 1.2s. In your case, it will sync up within a day. NTP is very clever so you never have newer files back-dated to be older than older files or vice versa. Spencer

Re: ntpd clock sync

2016-03-10 Thread Robert Coli
On Wed, Mar 9, 2016 at 9:03 AM, K F wrote: > the clock is about 30 to 40 seconds behind. > If you don't want to get ntp working there, why not just... manually... set the clocks? =Rob

Re: ntpd clock sync

2016-03-09 Thread K F
the clock is about 30 to 40 seconds behind. From: Jack Krupansky To: user@cassandra.apache.org Sent: Wednesday, March 9, 2016 11:31 AM Subject: Re: ntpd clock sync How far out of sync are the nodes? A few minutes or less? Many hours? Worst case, you could simply take the entire

Re: ntpd clock sync

2016-03-09 Thread Jack Krupansky
ready exists. In this case, the existing data (with timestamps in the > future) may take precedence over new writes (with correct timestamps). > > > > From: K F > Reply-To: "user@cassandra.apache.org", K F > Date: Wednesday, March 9, 2016 at 8:23 AM > To: User >

Re: ntpd clock sync

2016-03-09 Thread Jeff Jirsa
already exists. In this case, the existing data (with timestamps in the future) may take precedence over new writes (with correct timestamps). From: K F Reply-To: "user@cassandra.apache.org", K F Date: Wednesday, March 9, 2016 at 8:23 AM To: User Subject: ntpd clock sync H

ntpd clock sync

2016-03-09 Thread K F
Hi, I have question about ntpd. In certain clusters where new datacenters were added since 1 week we stood-up those machines didn't have ntpd running on them. Will it cause any problem if we enable or start ntpd now on those newly added datacenters.  Thanks.