Return-Path: X-Original-To: apmail-hadoop-common-user-archive@www.apache.org Delivered-To: apmail-hadoop-common-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 C22DCEAFA for ; Fri, 11 Jan 2013 06:05:49 +0000 (UTC) Received: (qmail 6639 invoked by uid 500); 11 Jan 2013 06:05:45 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 6351 invoked by uid 500); 11 Jan 2013 06:05:44 -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 6311 invoked by uid 99); 11 Jan 2013 06:05:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Jan 2013 06:05:42 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of harsh@cloudera.com designates 209.85.223.170 as permitted sender) Received: from [209.85.223.170] (HELO mail-ie0-f170.google.com) (209.85.223.170) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Jan 2013 06:05:35 +0000 Received: by mail-ie0-f170.google.com with SMTP id k10so1905573iea.15 for ; Thu, 10 Jan 2013 22:05:14 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:x-gm-message-state; bh=2xeqlkDYYB8vAJHHGhlfwZ0iV5afdI+Nfnl9e6D2oSw=; b=ep1lGg8I+Ij2NboWp5lIIUWC4edMwMXFgWcqs+9cwUXmCLMYEP27eeON2lVgKjIFPN Z3Aa85vZ4uXoaYyWgMPDHWD9ISDOxyLVhdM4Y1uLyaNO2zNNnmRU0BHoasxL4wcjC4Co ruYX9Q/rkz1qVvQ09EpG/TJtuYG72AfypD2Oo6tm6b3PMfnUEiOdmMTu5bvNvUZsJfGI /oMaZ/xl10uc+W4yZOvzM7GCJZp1kTqSfPin27sC2DBwCpcSfe5IjB0PLE6H18jKi8i4 GsmRCk0CbbECfuAvX95TQlOnInTvY2OtkZH4VMwVzouEjZIVYTrz+tjocQyLomr84HnQ V/Jw== X-Received: by 10.50.57.234 with SMTP id l10mr7933306igq.18.1357884314177; Thu, 10 Jan 2013 22:05:14 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.32.166 with HTTP; Thu, 10 Jan 2013 22:04:54 -0800 (PST) In-Reply-To: References: From: Harsh J Date: Fri, 11 Jan 2013 11:34:54 +0530 Message-ID: Subject: Re: queues in haddop To: "" Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQlKx6C1bNpWuIt+ldiXNjtsciQdFICEC52i/oBamPKrcn5HjegtwwECZFT6Z3SMg6MtaT9U X-Virus-Checked: Checked by ClamAV on apache.org Your question in unclear: HDFS has no queues for ingesting data (it is a simple, distributed FileSystem). The Hadoop M/R and Hadoop YARN components have queues for processing data purposes. On Fri, Jan 11, 2013 at 8:42 AM, Panshul Whisper wrote: > Hello, > > I have a hadoop cluster setup of 10 nodes and I an in need of implementing > queues in the cluster for receiving high volumes of data. > Please suggest what will be more efficient to use in the case of receiving > 24 Million Json files.. approx 5 KB each in every 24 hours : > 1. Using Capacity Scheduler > 2. Implementing RabbitMQ and receive data from them using Spring Integration > Data pipe lines. > > I cannot afford to loose any of the JSON files received. > > Thanking You, > > -- > Regards, > Ouch Whisper > 010101010101 -- Harsh J