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

Make resource manager pluggable #3

Open
hectcastro opened this issue Mar 5, 2015 · 6 comments
Open

Make resource manager pluggable #3

hectcastro opened this issue Mar 5, 2015 · 6 comments

Comments

@hectcastro
Copy link

Right now, the resource manager referenced in spark.js targets YARN specifically. It would be great to have support for both YARN and Mesos.

@ryan-williams
Copy link
Member

Good idea! I've never actually run Spark on Mesos so someone who has will probably be better suited to taking this on.

@hectcastro
Copy link
Author

Going to mess with it soon because I want to take advantage of all of the work already done here. Just wanted to put it out there in case anyone else already started down the path.

Thanks, @ryan-williams!

@ryan-williams
Copy link
Member

excellent, thanks for your help

@seregasheypak
Copy link

Hi, we are not using YARN currently, what could be an approach to gather apps ids from master or spark-history server?

@ryan-williams
Copy link
Member

Good question @seregasheypak. It seems like it should be straightforward to make a request to Spark history server instead of YARN RM, and scrape the results.

Alternatively, once Spark-4435 goes in (which seems like will be soon), maybe there will be a JSON endpoint that you can get a more structured form of that data from?

I'd start with just scraping the history server (unless there's already a JSON endpoint that will work).

Let me know if you are interested in working on that, otherwise I'll see if I can get to it.

@seregasheypak
Copy link

Got it, will report back in few days.

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

3 participants