Return-Path: Delivered-To: apmail-hadoop-chukwa-dev-archive@minotaur.apache.org Received: (qmail 68729 invoked from network); 16 Jun 2009 08:21:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 16 Jun 2009 08:21:11 -0000 Received: (qmail 9665 invoked by uid 500); 16 Jun 2009 08:21:22 -0000 Delivered-To: apmail-hadoop-chukwa-dev-archive@hadoop.apache.org Received: (qmail 9644 invoked by uid 500); 16 Jun 2009 08:21:22 -0000 Mailing-List: contact chukwa-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: chukwa-dev@hadoop.apache.org Delivered-To: mailing list chukwa-dev@hadoop.apache.org Received: (qmail 9634 invoked by uid 99); 16 Jun 2009 08:21:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Jun 2009 08:21:22 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of asrabkin@gmail.com designates 209.85.221.178 as permitted sender) Received: from [209.85.221.178] (HELO mail-qy0-f178.google.com) (209.85.221.178) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Jun 2009 08:21:14 +0000 Received: by qyk8 with SMTP id 8so5766563qyk.5 for ; Tue, 16 Jun 2009 01:20:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=XJb5jOO7TzaSBu5+xMppGCH0xU0UNFp9yAkZ+zG2TXo=; b=tdNWBnt4h9enexoGKrEPa4CejDSo2Qf8PqjWUxIN+5Yu0Y+ljk2wFCpeGtCNv8UpMJ e8caOYRDN7TrYC76O51/uyfU94i4VyCckN060q3GzHcwx8L4DxDq2utYsOC7isLU30Xd 5U/HY3N1vrF3wsUEzvrIEQP5GwmlbBeuqefcc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=USy+8jig81CzklXDFB08eRp+Djg9FlFG4UvdoyH6WcphlA9hd049WnO1+9iGjpC4WR vwIt5joNyGse/qAJUip7GxFUIcbgUXkzaIMGLFj0salY3N8+Qd4cdho/EEK4O+Sw4dhv NyAakOe2EcJP6jUwBzUzBCmEd+IZ0RpJCYAHE= MIME-Version: 1.0 Received: by 10.220.71.6 with SMTP id f6mr5511943vcj.16.1245140453513; Tue, 16 Jun 2009 01:20:53 -0700 (PDT) In-Reply-To: <9b40bc2a0906152202s7cc008c5r725cd588988da01b@mail.gmail.com> References: <39b0afc00906092309s39eb155ft47950d1724a6dc40@mail.gmail.com> <9b40bc2a0906152202s7cc008c5r725cd588988da01b@mail.gmail.com> Date: Tue, 16 Jun 2009 01:20:49 -0700 Message-ID: <39b0afc00906160120j29f16d2s60b5f1c0bf4ef331@mail.gmail.com> Subject: Re: timestamps and timezones From: Ariel Rabkin To: chukwa-dev@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org I don't believe NTP helps here. NTP keeps the clocks accurate, but you still need to think about time zones. On Mon, Jun 15, 2009 at 10:02 PM, Vijay wrote: > We in production use NTP for sync do we really need to worry abt this? > Regards, > > > > > On Tue, Jun 9, 2009 at 11:09 PM, Ariel Rabkin wrote: > >> timezones > -- Ari Rabkin asrabkin@gmail.com UC Berkeley Computer Science Department