Thank Danny and Dave, Your explanations are nice and clear.
so in that case does it means that ntp protocol cannot be load balanced at all?? are there any ways to provide load balancing without disturbing ntp roundtrip proccess? since i have gotten a lot of devices here , i made a simple design that all servers have their own public ip adresses. but my concern is that design is my clients can handle only 4 ntp servers, and to fit the requirement of 1million synch per poll, i will need 8 servers at least.. do you guys have any design idea that can handle such traffic after blackout for example? your help is really appreciated > From: [email protected] > Date: Tue, 27 Dec 2011 05:30:13 +0000 > To: [email protected] > CC: [email protected]; "terje.mathisen at tmsw.no"@ntp.org > Subject: Re: [ntp:questions] ntp server pool advice > > On Tue, Dec 27, 2011 at 03:39, Danny Mayer <[email protected]> wrote: > > You can use round robin dns for NTP. There's nothing wrong with that. > > It's load balancing that must NOT be used as you would get different > > answers from different systems each time. > > Danny is right here, though there's an exception implied by his > explanation: If your load balancing solution is mapping the same > address/port pairs to the same backend server for the most part, you > can use it for NTP service with less negative impact, vs. load > balancing each request to a potentially different backend server. > > The key point is ntpd assumes each remote address represents a single > oscillator. State is kept by ntpd clients for each association, > especially the clock filter register, so that unpredictable load > balancing will foul time transfer. > > Cheers, > Dave Hart > _______________________________________________ > questions mailing list > [email protected] > http://lists.ntp.org/listinfo/questions _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
