e the numbers for FILE_BYTES_READ/WRITTEN coming from?
TIA
Raj
From: Harsh J
To: common-user@hadoop.apache.org; R V
Sent: Thursday, July 28, 2011 12:03 AM
Subject: Re: File System Counters.
Raj,
There is no overlap. Data read from HDFS FileSystem instances go to
HDFS_BYTES_READ, and data read
Raj,
There is no overlap. Data read from HDFS FileSystem instances go to
HDFS_BYTES_READ, and data read from Local FileSystem instances go to
FILE_BYTES_READ. These are two different FileSystems, and have no
overlap at all.
On Thu, Jul 28, 2011 at 5:56 AM, R V wrote:
> Hello
>
> I don't know if
> Could the communication between blade server and disk array be the bottleneck?
Yes, depending on the number of blades, the network into the array
will bottleneck because it doesn't scale with the number of data
nodes.
I also have the idea in my mind. I want to install the hadoop cluster
in serveral blade servers, which are connected with a disk array. Data
is storaged in the disk array, and the blade servers are used for
computation.
Can MapReduce benefit from such architecture?
Could the communication between b
My setup is an existing farm based on a central Netapp, looking to scale out
and considering hadoop as a data processing / DWH alternative. Does this add
any relevant details to the answer?
Thanks.
On Tue, Dec 22, 2009 at 6:34 PM, Brian Bockelman wrote:
> Things to consider are cost, reliability,
Things to consider are cost, reliability, scalability, and what equipment you
might already own.
- SAN / NAS: generally less reliable than HDFS in terms of "how much data do
you lose if lightning strikes a box?". Many SAN/NAS solutions start with the
assumption that a given piece of hardware w
