Thanks both of you. It's very helpful
On Tue, Jul 14, 2009 at 8:13 AM, Amr Awadallah wrote:
> Mu,
>
> Though not a very good excuse, Hadoop wasn't originally designed for
> interactive latency, rather it focused on large scale throughput. That said,
> the hadoop developer community is working o
Mu,
Though not a very good excuse, Hadoop wasn't originally designed for
interactive latency, rather it focused on large scale throughput. That
said, the hadoop developer community is working on improving the startup
time for map-reduce jobs. Owen/Arun made a number of custom changes for
th
Hi Mu,
Small job overhead is something that has been worked on a bit in recent
versions, but here's the gist of it (as best as I know, though I don't work
much in this area of the code):
- The JobTracker doesn't assign tasks forcefully to TaskTrackers. Instead,
the TaskTrackers send heartbeats at
Hi, everyone
I've tested the hadoop environment I've set up. I noticed that it takes 24s
to run a 2 mapper, 1 reducer job with empty input.
Is it a reasonable time to run a do-nothing job? Why it takes so much time?
Thanks
--
Best wishes,
Qiao Mu
MOE KLINNS Lab and SKLMS Lab, Xi'an Jiaotong Uni
