As I understand it, this will not quarantee that they are millisecond accurate which is what you need for Cassandra to use the correct commit. We've seen problems in production and had to rearchitect parts of the system due to this even though all servers are NTP synched.
http://www.endruntechnologies.com/faq.htm#How_accurate_is On Mon, Jul 25, 2011 at 1:38 PM, Sooraj S <soor...@sparksupport.com> wrote: > may be you can sync the servers with "pool.ntp.org" with running ntp as a > service. > > > On 25 July 2011 14:34, Paul Loy <ketera...@gmail.com> wrote: > >> And I guess there's the next problem, if you have more than one client... >> >> >> On Mon, Jul 25, 2011 at 5:25 AM, Edward Capriolo >> <edlinuxg...@gmail.com>wrote: >> >>> You should always sync your host clocks. Clients provide timestamp but >>> for the server gc_grace and ttl columns can have issues if server clocks are >>> not correct. >>> >>> On Sunday, July 24, 2011, 魏金仙 <sei_...@126.com> wrote: >>> > hi all, >>> > I'm launching a cassandra cluster with 30 nodes. I wonder whether >>> the inconsistency of host clocks will influence the performance of cluster. >>> > Thanks! >>> > >>> > >>> >> >> >> >> -- >> --------------------------------------------- >> Paul Loy >> p...@keteracel.com >> http://uk.linkedin.com/in/paulloy >> > > > > -- > Thanks & Regards > SOORAJ S > > > http://SparkSupport.com | http://migrate2cloud.com > Thanks and Regards, > Sooraj S > Software Engineer > **** > -- --------------------------------------------- Paul Loy p...@keteracel.com http://uk.linkedin.com/in/paulloy
