:) Great. Thanks for the input. :)
On Mon, Jan 7, 2013 at 3:31 PM, Pamecha, Abhishek apame...@ebay.com wrote:
You will incur the cost of map reduce across all nodes in your cluster
anyways. Not sure, you will get enough speed advantage.
HBase may help you get close to what you are
Hi all,
does anyone get UnsupportedActionException when start balancer in
hadoop-2.0.2 alpha?
any file need to configure for balancer?
starting balancer, logging to
/hadoop/hadoop-2.0.2/logs/hadoop-root-balancer-hve-test1.out
Hello there,
Thank you for the comments. But, just to let you know,
it's a community work and no one in particular can be held
responsible for these kind of small things. This is how open
source works. Guys who are working on Hadoop have a lot
of things to do. In spite of that, they are
Make sure all the config settings are OK and you have proper dns
resolution. Modify the line 127.0.1.1 in your /etc/hosts file to
127.0.0.1. And, I completely agree with Vinod sir. 0.14 is ancient now.
HTH
P.S : you can go
Just a little clarification
This is NOT how open source works by any means as there are many Open Source
projects with well written and maintained documentation.
It all comes down to the 2 Open Source models
1. ASF Open Source - which is a pure democracy or may be even anarchy without
any
No, I was not talking about wrappers of ASF projects. I was referring to
non-ASF Open Source projects all together (e.g., GitHub, SourceForge, Google
code etc.).
Oleg
On Jan 8, 2013, at 8:20 AM, Glen Mazza gma...@talend.com wrote:
quote: Obviously in the second there is a vested interested
Hi,
I am not sure if your complaint is as much about the changing interfaces as
it is about documentation.
Please note that versions prior to 1.0 did not have stable interfaces as a
major requirement. Not by choice, but because the focus was on seemingly
more important functionality, stability,
Your output shows that node2 has 13 mappers and the reducer, while
node3 and node4 had only 8 mappers each. So I'd expect some
disparity. Since it's hard to correlate the mapper throughput against
the reducer throughput, it's possible that node3 got just as much work
done.
That doesn't explain
