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 8984911BE6 for ; Thu, 12 Jun 2014 22:04:43 +0000 (UTC) Received: (qmail 55808 invoked by uid 500); 12 Jun 2014 22:04:39 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 55721 invoked by uid 500); 12 Jun 2014 22:04:38 -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 55714 invoked by uid 99); 12 Jun 2014 22:04:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Jun 2014 22:04:38 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE X-Spam-Check-By: apache.org Received-SPF: unknown (athena.apache.org: error in processing during lookup of john.lilley@redpoint.net) Received: from [206.225.164.222] (HELO hub021-nj-6.exch021.serverdata.net) (206.225.164.222) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Jun 2014 22:04:32 +0000 Received: from MBX021-E3-NJ-2.exch021.domain.local ([10.240.4.78]) by HUB021-NJ-6.exch021.domain.local ([10.240.4.92]) with mapi id 14.03.0174.001; Thu, 12 Jun 2014 15:04:09 -0700 From: John Lilley To: "user@hadoop.apache.org" Subject: RE: Hadoop SAN Storage reuse Thread-Topic: Hadoop SAN Storage reuse Thread-Index: Ac+GA4qca1/ZeRdUSzaJA4D+tDfQZwAhWJdA Date: Thu, 12 Jun 2014 22:04:09 +0000 Message-ID: <869970D71E26D7498BDAC4E1CA92226B86F2F6B9@MBX021-E3-NJ-2.exch021.domain.local> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [173.160.43.60] Content-Type: multipart/alternative; boundary="_000_869970D71E26D7498BDAC4E1CA92226B86F2F6B9MBX021E3NJ2exch_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_869970D71E26D7498BDAC4E1CA92226B86F2F6B9MBX021E3NJ2exch_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hadoop performs best when each node has exclusive use of its disk. Therefo= re, if you have a choice, try to provision exclusive use of individual spin= dles on your SAN and map each one to a separate mount on your Hadoop nodes.= Anything other than that will tend to produce poor performance due to dis= k contention. john From: Natarajan, Prabakaran 1. (NSN - IN/Bangalore) [mailto:prabakaran.1.na= tarajan@nsn.com] Sent: Thursday, June 12, 2014 12:00 AM To: user@hadoop.apache.org Subject: Hadoop SAN Storage reuse Hi I know SAN storage is not recommended for Hadoop. But we don't want wast= e - already existing SAN Storage. How can we make use of SAN Storage for Hadoop - what are the best methods, = can a Ethernet upgrade helps,...? Thanks Prabakaran.N --_000_869970D71E26D7498BDAC4E1CA92226B86F2F6B9MBX021E3NJ2exch_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hadoop performs best when= each node has exclusive use of its disk. Therefore, if you have a ch= oice, try to provision exclusive use of individual spindles on your SAN and map each one to a separate mount on your Hadoop nodes. = Anything other than that will tend to produce poor performance due to disk = contention.

<= /p>

john

<= /p>

From: Nataraja= n, Prabakaran 1. (NSN - IN/Bangalore) [mailto:prabakaran.1.natarajan@nsn.co= m]
Sent: Thursday, June 12, 2014 12:00 AM
To: user@hadoop.apache.org
Subject: Hadoop SAN Storage reuse

I know SAN storage is not recommended f= or Hadoop. But we don’t want waste – already = existing SAN Storage.

How can we make use of SAN Storage for = Hadoop – what are the best methods, can a Ethernet upgrade helps,R= 30;?

Thanks

Prabakaran.N

--_000_869970D71E26D7498BDAC4E1CA92226B86F2F6B9MBX021E3NJ2exch_--