Return-Path: Delivered-To: apmail-hadoop-core-user-archive@www.apache.org Received: (qmail 13741 invoked from network); 25 Feb 2009 18:14:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 Feb 2009 18:14:20 -0000 Received: (qmail 26504 invoked by uid 500); 25 Feb 2009 18:14:13 -0000 Delivered-To: apmail-hadoop-core-user-archive@hadoop.apache.org Received: (qmail 26464 invoked by uid 500); 25 Feb 2009 18:14:13 -0000 Mailing-List: contact core-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-user@hadoop.apache.org Delivered-To: mailing list core-user@hadoop.apache.org Received: (qmail 26453 invoked by uid 99); 25 Feb 2009 18:14:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Feb 2009 10:14:13 -0800 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 greycat.na.kor@gmail.com designates 209.85.218.179 as permitted sender) Received: from [209.85.218.179] (HELO mail-bw0-f179.google.com) (209.85.218.179) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Feb 2009 18:14:07 +0000 Received: by bwz27 with SMTP id 27so116896bwz.29 for ; Wed, 25 Feb 2009 10:13:45 -0800 (PST) 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=kSHOfJXDPDK4ZdmStr61ObCFIc9hj1lpFQcwy+pyfRE=; b=yEN9LvGGV7LrO2eTSkk6JvKb1F/V5pq5XkNF1s0blTfw7/24jLpBXnakrD1zJXHju9 +ySwUHlcO7nXwckwVVYG56zUn1/T44DFZG5laz0WmFdhIpAgqn5ulcNS/lYrOXaKCwrQ vZPYat/Q4f8RA2RFNdrTYsyqLyMM2TcT8FL68= 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=YiyfoAYyTR5+89sErHkw8nlV62M96QPIVK9PbEufhwSzZWSqWea7f7H8bJBS9a3Mzl z+emKM5joetYhTt6POvJO/8GL5p91n8tEW+aMzaHkateSb8vCCdPM/lBa3rybNXcQf7y bGGTSpT1nGAVvUA/k3zPJjeRJNJApZ0jzfYwE= MIME-Version: 1.0 Received: by 10.103.11.7 with SMTP id o7mr184572mui.103.1235585625227; Wed, 25 Feb 2009 10:13:45 -0800 (PST) In-Reply-To: <6acdaf2a0902250559j6ff97e5cq989c135ebfcfaab9@mail.gmail.com> References: <6acdaf2a0902250559j6ff97e5cq989c135ebfcfaab9@mail.gmail.com> Date: Wed, 25 Feb 2009 21:13:45 +0300 Message-ID: <240e377b0902251013l6d905317y5119c1d23dd1ad70@mail.gmail.com> Subject: Re: Using Hadoop for near real-time processing of log data From: Mikhail Yakshin To: core-user@hadoop.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, > Is anyone using Hadoop as more of a near/almost real-time processing > of log data for their systems to aggregate stats, etc? We do, although "near realtime" is pretty relative subject and your mileage may vary. For example, startups / shutdowns of Hadoop jobs are pretty expensive and it could take anything from 5-10 seconds up to several minutes to get the job started and almost same thing goes for job finalization. Generally, if your "near realtime" would tolerate 3-4-5 minutes lag, it's possible to use Hadoop. -- WBR, Mikhail Yakshin