Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Kafka >> mail # user >> Auditing system clocks


Copy link to this message
-
Re: Auditing system clocks
It is assumed that clocks are in sync, we use ntp and it mostly works.

-Jay
On Tue, Sep 24, 2013 at 5:12 PM, Tom Amon <[EMAIL PROTECTED]> wrote:

> I've read in the docs and papers that LinkedIn has an auditing system that
> correlates message counts from tiers in their system using a time window of
> 10 minutes. The time stamp on the message is used to determine which window
> the message falls into.
>
> My question is how do you account for clock drift between machines? Is it
> assumed that clocks are in sync?
>
> Thanks.
>

 
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB