in
production, to reduce the amount of downtime if you need to replace or
restart your namenode. If that isn't a concern for you then you don't need
it.
On Mon, Dec 17, 2012 at 12:04 PM, Ivan Ryndin iryn...@gmail.com wrote:
Hi all,
is it necessary to run secondary namenode when starting
Harsh,
can you please tell will 2.0.3 release be ready to the end of Jan 2013?
Regards,
Ivan
2012/12/13 Harsh J ha...@cloudera.com
If your production target is bit far away, I'd encourage setting up
and using the 2.x based releases for its feature set that may aid you
in your design.
Hi all!
What are the best practices to start MR jobs?
Curently I start my jobs by cron.
Also I start jobs by internal timer from my java application (which is
similar starting by cron)
What are other approaches to start MR jobs?
Perhaps, some best practices apply here?
--
Best regards,
Ivan
