Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 26A0A11BC2 for ; Mon, 12 May 2014 00:31:24 +0000 (UTC) Received: (qmail 4386 invoked by uid 500); 10 May 2014 23:19:37 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 48457 invoked by uid 500); 10 May 2014 23:07:17 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 96901 invoked by uid 99); 10 May 2014 22:56:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 May 2014 22:56:11 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of dechouxb@gmail.com designates 209.85.215.46 as permitted sender) Received: from [209.85.215.46] (HELO mail-la0-f46.google.com) (209.85.215.46) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 May 2014 13:46:45 +0000 Received: by mail-la0-f46.google.com with SMTP id ec20so437238lab.5 for ; Fri, 09 May 2014 06:46:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=LR9lq2gx6PI4L3Qe5kvSv9RytnzuVmENQTh9baMtsDI=; b=efDpAgu22sA3JH6G4r1ElaZUf0HooeEI3RJInt9rEBHrMx8MR0rLtJ29QB2J1U5vH0 qhEP2qQ8Gox1YQqg0W2eP4sdN8Ywhr9qpusGNHINIuQDewSdaluN/xtm1XUkY/ug4qAY WCC+oLst1lz2P/pTaeD1Y12KtQRwFW2frjrsDVjBFeeS0JBRX4eRp4aMYiafJqys+E/V eKklaI5StdGwxMoQU7tV7DDmfJ0Vbh7ssNwqsJgCoJMLd7+k3i0eETIiCmaVr7fYRZQe KPpQbvUcBeFdA+q3GxITHDZGmyA6xRZm1b/PqDU2gr+rYl/n5/ylid1cZve1hPFFfjHx ou8Q== MIME-Version: 1.0 X-Received: by 10.152.203.168 with SMTP id kr8mr2047058lac.17.1399643184368; Fri, 09 May 2014 06:46:24 -0700 (PDT) Received: by 10.112.51.1 with HTTP; Fri, 9 May 2014 06:46:24 -0700 (PDT) In-Reply-To: References: <11564200.Tc0LUDiuXJ@f6-dat6-306-27> Date: Fri, 9 May 2014 15:46:24 +0200 Message-ID: Subject: Re: Realtime sensor's tcpip data to hadoop From: Bertrand Dechoux To: "user@hadoop.apache.org" , user@flume.apache.org Content-Type: multipart/alternative; boundary=001a113457dcd1123e04f8f7d263 X-Virus-Checked: Checked by ClamAV on apache.org --001a113457dcd1123e04f8f7d263 Content-Type: text/plain; charset=UTF-8 Flume is indeed something you should look into. 'Log files' is a simplification. Flume really handles events and yes logs are a common kind of event but not the only one. Regards Bertrand On Wed, May 7, 2014 at 4:48 AM, Alex Lee wrote: > Sensors' may send tcpip data to server. Each sensor may send tcpip data > like a stream to the server, the quatity of the sensors and the data rate > of the data is high. > > Firstly, how the data from tcpip can be put into hadoop. It need to do > some process and store in hbase. Does it need through save to data files > and put into hadoop or can be done in some direct ways from tcpip. Is there > any software module can take care of this. Searched that Ganglia Nagios and > Flume may do it. But when looking into details, ganglia and nagios are > more for monitoring hadoop cluster itself. Flume is for log files. > > Secondly, if the total network traffic from sensors are over the limit of > one lan port, how to share the loads, is there any component in hadoop to > make this done automatically. > > Any suggestions, thanks. > --001a113457dcd1123e04f8f7d263 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Flume is indeed something you should look into. 'Log f= iles' is a simplification. Flume really handles events and yes logs are= a common kind of event but not the only one.

Regards

Bertrand

On Wed, May 7, 2014 at 4:48 AM, Alex Lee <eliyart@hotma= il.com> wrote:
Sensors'=C2=A0may send tcpip data to server. Each= sensor may send tcpip=C2=A0data like a stream to the server, the quatity o= f the sensors and the data rate of the data is high.
=C2=A0
Firstly, = how the=C2=A0data from tcpip can be put into hadoop. It need to do some pro= cess and store in hbase. Does it need through save to=C2=A0data files and p= ut into hadoop=C2=A0or can be done in some=C2=A0direct ways from tcpip. Is = there any software module can take care of this.=C2=A0Searched that=C2=A0Ga= nglia=C2=A0Nagios and Flume may do it. But when looking into details, gangl= ia and nagios are more=C2=A0for monitoring hadoop cluster itself. Flume is = for log files.
=C2=A0
Secondly, if=C2=A0the=C2=A0total network traffic from sensors are= over the limit of one lan port, how to share the loads, is there any compo= nent in hadoop to make this done automatically.
=C2=A0
Any suggestion= s, thanks.

--001a113457dcd1123e04f8f7d263--