Federation is coming to Hadoop. It sounds like it will solve the problems with having a single name node. Will federation also benefit MapR?

asked 26 Jun '11, 08:03

FAQ's gravatar image

FAQ ♦
147363739
accept rate: 0%


Federation does get rid of having a single name node which allows Hadoop clusters to have more files by a small factor, but it doesn't solve the problems of having a single name node. The problems with a single name node are scalability and reliability. With federation, the problem of scalability is eased a little bit, but definitely not solved because the low performance inherent with sending all meta-data requests through one or a few hosts still remain.

The problem of reliability just get worse with federation because the previous single point of failure is multiplied. Looking only at hardware reliability, if you have ten name nodes, the mean time between hardware failures for your cluster is likely to decrease to a few months down from the current level of a few years. Of course, human fallibility normally increases these failure rates significantly. MapR addresses both hardware and human failure modes and also provides much higher scalability than Apache Hadoop.

link

answered 26 Jun '11, 08:16

TedDunning's gravatar image

TedDunning ♦♦
3.3k318
accept rate: 22%

edited 26 Jun '11, 09:35

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×71
×1

Asked: 26 Jun '11, 08:03

Seen: 1,651 times

Last updated: 26 Jun '11, 09:35

powered by OSQA