One benefit is that if your map or reduce behaves badly it can't take
down the task tracker.
In our case we have some poorly behaved external native libraries we
use, and we have to forcibly ensure that the child vms are killed when
the child main finishes (often by kill -9), so the fact the child (task)
is a separate jvm process is very helpful.
The downside is the jvm start time. Has anyone experimented with the jar
freezing for more than the standard boot class path jars to speed up
startup?
Shengkai Zhu wrote:
What's the benefits from such design compared to multi-thread?
--
Jason Venner
Attributor - Program the Web <http://www.attributor.com/>
Attributor is hiring Hadoop Wranglers and coding wizards, contact if
interested
