Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better support for HA JobTrackers #28

Open
tarnfeld opened this issue Jul 6, 2014 · 0 comments
Open

Better support for HA JobTrackers #28

tarnfeld opened this issue Jul 6, 2014 · 0 comments

Comments

@tarnfeld
Copy link
Member

tarnfeld commented Jul 6, 2014

I've not got this up and running yet, so just thinking it through. It'd be great (and a requirement for me) to support HA jobtrackers. I think there are a couple of small issues that currently prevent that, though please correct me if i'm wrong. Is anyone else successfully running HA JobTrackers on Mesos?

  • Don't set the mapred.job.tracker option to a host:port combo. This isn't how HA jobtrackers work, you list (elsewhere in configuration) the name:host:port combo's and reference them with an alias here. Due to the way the configuration is passed to the TaskTrackers, the only issues I can find here is Don't set the mapred.job.tracker config option #27. I can confirm with this fix applied I can at least get TT's to launch and run with HA jobtracker config.
  • Allow all JobTracker's to register with the same Mesos framework ID. When using the automatic JobTracker failover (using the ZooKeeper Failover Controller) feature hadoop will keep all jobs and tasks running, however I think due to the fact each MesosScheduler will register with it's own framework identifier all the TaskTrackers will be killed. If they both register and use a large failover timeout, would this issue be solved?

Looking forward to anyone's thoughts...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant