HBase is a database that runs on top of HDFS. So that's another one. It has an
append-only usage pattern, which makes it a good fit.
I don't see how not-so-commodity hardware could go without replication to
achieve the same as HDFS. It's not only about data safety, but also about
availability.
Hi,
For true data durability RAID is not enough.
The conditions I operate on are the following:
(1) Data loss is not acceptable under any terms
(2) Data unavailability is not acceptable under any terms for any period of
time.
(3) Data loss for certain data sets become a legal issue and is again n
The smallest size in HDFS is not the blocksize. The blocksize is an upper
limit, but if you store smaller files it will not take up extra space.
HDFS is not meant for fast random access but built specifically for large
files and sequential access.
On Wed, Jan 26, 2011 at 9:59 AM, Gerrit Jansen
Ok. Is your statement, "I use HDFS for general-purpose data storage because it
does this replication well", or is it more, "the most important benefit of
using HDFS as the Map-Reduce or HBase backend fs is data safety." In other
words, I'd like to relate this back to my original question of th
What is the default timeout value to detect a dead node? I would like to
decrease this if possible
Rita
I believe for most people, the answer is "Yes"
-Original Message-
From: Nathan Rutman
Date: Wed, 26 Jan 2011 09:41:37
To:
Reply-To: hdfs-user@hadoop.apache.org
Subject: Re: HDFS without Hadoop: Why?
Ok. Is your statement, "I use HDFS for general-purpose data storage because it
does t
I believe for most people, the answer is "Yes"
-Original Message-
From: Nathan Rutman
Date: Wed, 26 Jan 2011 09:41:37
To:
Reply-To: hdfs-user@hadoop.apache.org
Subject: Re: HDFS without Hadoop: Why?
Ok. Is your statement, "I use HDFS for general-purpose data storage because it
does t
