Return-Path: X-Original-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-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 E7ED511408 for ; Fri, 6 Jun 2014 18:20:31 +0000 (UTC) Received: (qmail 48518 invoked by uid 500); 6 Jun 2014 18:20:26 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 48396 invoked by uid 500); 6 Jun 2014 18:20:26 -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 48389 invoked by uid 99); 6 Jun 2014 18:20:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jun 2014 18:20:25 +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 (athena.apache.org: domain of vinodkv@hortonworks.com designates 209.85.160.50 as permitted sender) Received: from [209.85.160.50] (HELO mail-pb0-f50.google.com) (209.85.160.50) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jun 2014 18:20:21 +0000 Received: by mail-pb0-f50.google.com with SMTP id ma3so2781642pbc.37 for ; Fri, 06 Jun 2014 11:20:00 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :message-id:references:to:content-type:content-transfer-encoding; bh=72rfjBz3s2DPHAIcuufsIlSJ+PgdYN4WJVTdo0Dx6ik=; b=Vvdcsv5PAwvUKKOSpladY9sgP96pxWWfbc22JMb7irobpgzB0XzhJ+oTSVx2LDoMF2 dsE4iADGKxnufHd5CFvyk+0Lw2s97xsXVepg2tQHd5x4deo1QBh/vYfyBVlw05FN6NSn wRdcaZJUx4IlOwTxc64YfCs1PqA/lZECN9m9daPf3nX/b1lpAAzzbRhR4k7T9xHNDBDQ D0yXM/GZ2yNqsXfe8NmDYVDEvaxI95FUc3g+aM2FUYn94bEAvJoa+FL5BJE/FaQLel+s NTAHfH4+2XvtcFK8nBKstxqch8IfyQz5lqY0OMor99mLFv2p2yAhsrxpb2v2c8yVqMRN XIIA== X-Gm-Message-State: ALoCoQmHpcWYSqeK0uHUCwgloyvrpo5gLywfKrOHoQHYjbFyTjlIXsJ4g4qNMBuyIbRrHWNTZKln3abgPz+roJ9j5gQhA04ByNf92IE7lPIvZjR+59fRuYg= X-Received: by 10.68.131.227 with SMTP id op3mr3440721pbb.87.1402078799803; Fri, 06 Jun 2014 11:19:59 -0700 (PDT) Received: from [10.11.2.182] ([192.175.27.2]) by mx.google.com with ESMTPSA id co3sm38498666pbb.89.2014.06.06.11.19.57 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 06 Jun 2014 11:19:59 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) Subject: Re: Hadoop usage in uploading & downloading big data From: Vinod Kumar Vavilapalli In-Reply-To: Date: Fri, 6 Jun 2014 11:19:55 -0700 Message-Id: References: To: user@hadoop.apache.org X-Mailer: Apple Mail (2.1878.2) Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Can you give more details on the data that you are storing in "the release = data management"? And also how on how it is accessed - read, and modified? +vinod On Jun 2, 2014, at 5:33 AM, rahul.soa wrote: > Hello All, > I'm newbie to Hadoop and interested to know if hadoop can be useful in or= der to solve the problem I am seeing. > =20 > We have big data (sometimes b/w 200 - 600 GB) to store in the release dat= a management (repository server, currently we are using synchronicity desig= nsync) which takes roughly about 3-7 hours to upload/checkin this data (an= d download from repository server). > =20 > I would like to know if application of hadoop can be useful in order to r= educe this big time. The time taken is bothering design engineers to upload= and download which further lead to delay in deliveries. > =20 > Please note I'm new to hadoop and checking the possibility of usage in th= is scenario. > =20 > Best Regards, > Rahul --=20 CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to= =20 which it is addressed and may contain information that is confidential,=20 privileged and exempt from disclosure under applicable law. If the reader= =20 of this message is not the intended recipient, you are hereby notified that= =20 any printing, copying, dissemination, distribution, disclosure or=20 forwarding of this communication is strictly prohibited. If you have=20 received this communication in error, please contact the sender immediately= =20 and delete it from your system. Thank You.