Return-Path: X-Original-To: apmail-flume-user-archive@www.apache.org Delivered-To: apmail-flume-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 47BDA1015C for ; Tue, 1 Jul 2014 06:47:26 +0000 (UTC) Received: (qmail 19709 invoked by uid 500); 1 Jul 2014 06:47:25 -0000 Delivered-To: apmail-flume-user-archive@flume.apache.org Received: (qmail 19660 invoked by uid 500); 1 Jul 2014 06:47:25 -0000 Mailing-List: contact user-help@flume.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@flume.apache.org Delivered-To: mailing list user@flume.apache.org Received: (qmail 19650 invoked by uid 99); 1 Jul 2014 06:47:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Jul 2014 06:47:25 +0000 X-ASF-Spam-Status: No, hits=-0.5 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mgulyas86@gmail.com designates 209.85.212.170 as permitted sender) Received: from [209.85.212.170] (HELO mail-wi0-f170.google.com) (209.85.212.170) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Jul 2014 06:47:24 +0000 Received: by mail-wi0-f170.google.com with SMTP id cc10so6848936wib.3 for ; Mon, 30 Jun 2014 23:47:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=An4WhrPZcGeRL/KTi1ZUe9fx/9vWsfcUTCJP+iTod/k=; b=t9aeCZ2cOadZggEHOgQBo/z/lIAFp6/lP0KpVrinBbny8+yR8UCaABXT2TKxzaZSFi DS7vXw9qfsyRfpe4KkfQptO7Yt3MDDc0CMTUa5PBvxV73vtDFwueZRA40VJaGfRRrsRB KjoX4T8TT6OhLsuyl2rt+xGsZCVDsqjN48H0udthUDErb7IYVoEes/9bj6dsecd6P3Rk lDndGsSSLEB9QAzr/PQOMq+CLV9UnvpdK6ye8LfLOjsdR1NjWhuI9/i5XpPAbHIATQ17 nSMMtGXyRV4R1wQkGXX2LsMSzz8dhKjWiFyQiUPJCtQQAX5pzqBAwjSE97VLTlFBB8/i nh0A== MIME-Version: 1.0 X-Received: by 10.180.20.15 with SMTP id j15mr34738711wie.60.1404197220217; Mon, 30 Jun 2014 23:47:00 -0700 (PDT) Sender: mgulyas86@gmail.com Received: by 10.194.5.71 with HTTP; Mon, 30 Jun 2014 23:47:00 -0700 (PDT) In-Reply-To: References: Date: Tue, 1 Jul 2014 08:47:00 +0200 X-Google-Sender-Auth: SPDz2JlR4nhPjaDqw7nFwWyrTHE Message-ID: Subject: Re: Flume NG and S3 From: =?UTF-8?B?TcOhdMOpIEd1bHnDoXM=?= To: user@flume.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Please see my comments inline. YIMEN YIMGA Gael wrote: > Could you please communicate the link of the article you read please ? https://gist.github.com/crowdmatt/5256881 and the last comment. Sharninder wrote > No reason to not use flume except for the fact that S3, since its over th= e wire, will be a lot slower than a local hdfs cluster in which case you ne= ed a big enough channel to hold events not yet processed out of the sink. I= f you have a fast enough pipe, you can very well use flume for this sort of= use-case. I plan to aggregate 5-15GB data with Filechannel, as I want to flush to S3 every hour on every node. As far as I know Flume can gzip it, so the size would be about 500MB-1,5GB. Thanks for the feedback, I will write If I have any results. Mate Gulyas On Tue, Jul 1, 2014 at 6:26 AM, Sharninder wrote: > No reason to not use flume except for the fact that S3, since its over th= e > wire, will be a lot slower than a local hdfs cluster in which case you ne= ed > a big enough channel to hold events not yet processed out of the sink. If > you have a fast enough pipe, you can very well use flume for this sort of > use-case. > > The reason the author might have moved to kafka, and I'm just speculating > here, is that kafka provides him better buffering support for exactly the > case I've written above. > > HTH > Sharninder > > > > On Mon, Jun 30, 2014 at 7:57 PM, M=C3=A1t=C3=A9 Guly=C3=A1s wrote: >> >> Hi! >> >> I would like to use flume to aggregate and send logs to an S3 bucket. >> I did some research, but the last article I found on the topic was >> more then a year old and the author abandoned Flume for Kafka. My >> other concern is that most of the articles were written for Flume OG, >> not NG. >> Is there any reason why I should not use flume to sink messages to S3? >> >> >> Thanks in advance. >> >> Mate Gulyas >> Lead Developer at Dmlab > >