Billie, I agree with you. From what I read in the jira, all of their ³starter set² of requirements are supported by Slider. Slider has shortcomings on the monitoring side though, but if they can provide specifics (or file jiras) we can work with them to find a solution or alternatives.
I also see that there is a sense of misconception around Slider, that application owners need to familiarize themselves with Slider Java and Python code-base. It is required but only if they want to contribute to Slider, which would be awesome. Packaging format and Slider client cmd-line is all that they need to familiarize themselves with. Unless I see any further advanced set of requirements, I think they can save a lot of time and focus on Drill rather than YARN integration. -Gour On 4/6/16, 12:31 PM, "Billie Rinaldi" <billie.rina...@gmail.com> wrote: >There's a discussion on DRILL-1170 about whether they're going to >implement >their own AM or possibly use Slider. Initially they seemed to be leaning >against Slider, but there appears to be an opening: > >"if the Slider community co-implemented this with the Drill folk, it would >probably allow Slider to support more use cases and bring us to a shared >approach rather than two separate codebases. Do you think that anyone from >the Slider community would be able to spend substantial time against this >to address the Drill needs?" > >Any thoughts? > >[1]: https://issues.apache.org/jira/browse/DRILL-1170
