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
Kafka-mesos jar not found in current dir #172
Comments
@joestein Currently adding Jar support to http://github.com/mesos/logstash as well. Are you interested in a PR to solve this issue? |
Hey Frank, that sounds like an interesting addition. It is important to not break the functionality of the executor being independent from the scheduler it is how we can run different kafka broker binary versions through the scheduler. It is quite vital to working with kafka so you can run a different branch, patch or distro without being pinned to any one Kafka version/binary. If you can make a PR that solves the issue without changing and breaking the multiple version/binary compatibility that would be great. Maybe something like "if not specified/found" then use the scheduler supplied executor or something maybe that would work @dmitrypekar might have another recommend or maybe you can come up with an approach. |
I would recommend to add That approach seems to be straightforward and consistent with mechanism for specifying jre path that exists now. |
Instead of adding Jar support I added a minimesos quickstart script in #183 Steps to run Mesos Kafka
and off you go. |
I am getting this error on running the quickstart.sh script |
@jiteshsharma First build the Mesos Kafka Docker image in |
The problem
I tried running Kafka on minimesos and noticed that the scheduler requires the kafka-mesos jar to be available in the sandbox. See the stderr logs.
Steps to reproduce
Possible solution
How about packaging the executor jar inside the scheduler jar and serve it as a resource. We used this resource technique in Mesos Elasticsearch. See the SimpleFileServer and the Main which initializes the server with the Elasticsearch executor jar.
The text was updated successfully, but these errors were encountered: