Return-Path: X-Original-To: apmail-incubator-flume-user-archive@minotaur.apache.org Delivered-To: apmail-incubator-flume-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 7CB209F95 for ; Thu, 5 Jul 2012 12:38:22 +0000 (UTC) Received: (qmail 75619 invoked by uid 500); 5 Jul 2012 12:38:21 -0000 Delivered-To: apmail-incubator-flume-user-archive@incubator.apache.org Received: (qmail 75433 invoked by uid 500); 5 Jul 2012 12:38:20 -0000 Mailing-List: contact flume-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: flume-user@incubator.apache.org Delivered-To: mailing list flume-user@incubator.apache.org Received: (qmail 75397 invoked by uid 99); 5 Jul 2012 12:38:19 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jul 2012 12:38:19 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FSL_RCVD_USER,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of guidox@gmail.com designates 209.85.161.175 as permitted sender) Received: from [209.85.161.175] (HELO mail-gg0-f175.google.com) (209.85.161.175) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jul 2012 12:38:12 +0000 Received: by ggnp4 with SMTP id p4so6914543ggn.6 for ; Thu, 05 Jul 2012 05:37:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=d6G1ABWDlW9eAkvuVHryaVXipShbyzewWPnvPH3B61k=; b=uNm6solpXvH4mrzSt2/v3USUStNYwysNUvvS6TmkEkL3NFsADRa+cVxnfx9ASEgaZj RlYiD/ME7DOa/5CGBMIALlM3dK6pdSWskyOVieKomT+JYW+YrDLLJE9he/DVqaawXqPq 7W21NBmQO6GwugjhtIWTmKmgqL+ZpXQy4PH+t3y+FOTDlA9S9/bKpd/uKtnkvwNX2qga VI1O40IMp0rqd4HqEDUHyndZhZZX+vK/aO5XvJ5lV7HpdZ1JfPTt+NfQs8A7uEB1BmtN I6MvH13NvfqkyeHCXKZPW9RS3A43BMZuvyhoC+QeAaOH1ASXAjXspdphK+bBZZBMjNA3 9gIA== MIME-Version: 1.0 Received: by 10.101.176.37 with SMTP id d37mr9025848anp.20.1341491871285; Thu, 05 Jul 2012 05:37:51 -0700 (PDT) Received: by 10.236.114.132 with HTTP; Thu, 5 Jul 2012 05:37:51 -0700 (PDT) Date: Thu, 5 Jul 2012 14:37:51 +0200 Message-ID: Subject: Reliable flows in flume From: Guido Urdaneta To: flume-user@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Hi, I have been trying to configure a reliable flow in Flume NG. I installed the Flume NG distribution that comes with Cloudera cdh4. Cloudera's documentation says that JDBC channel is "ideal for flows where recoverability is important" and that FileChannel "is not yet ready for use". However, in some messages in this mailing list FileChannel has been recommended as the best option for reliable flows. Is this actually the case? Is Cloudera packing an old version of Flume NG with its CDH4 distribution? Any recommendations? I have found the performance of JDBC channel to be extremely slow (about 10,000 times slower than memory channel), with the bottleneck being CPU usage. Can anybody give a recommendation? Thanks in advance, GU