-
Notifications
You must be signed in to change notification settings - Fork 66
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
How to run this entirely under mesos #29
Comments
/etc/mesos/zk is introduced by mesosphere rpm package, not a work for all solution.
Not sure this is necessary, see storm fault tolerance
Does storm stores nimbus into zookeeper? I'm not sure. |
I'm not sure. At least the framework could check if /etc/mesos/zk exists and use it if it does. Ultimately, you shouldn't need to hardcode things if you're using mesos. That is after all, one of the biggest features, is that you don't care what server it runs on, so long as it does run :) |
I'll submit a PR as a python script which does this for you, is that ok? I'll register nimbus in zookeeper and then configure the UI to look at it. |
I think having it passed in to the framework and/or optionally looking at /etc/mesos/zk is fine. |
I got it all working, by adding a python wrapper script. The concept is documented here. What of this makes sense for the framework to natively do? |
I think PR #65 fixes this too -- it has a marathon launching script that will launch everything. @brndnmtthws : think we can close this? |
I've also spent a bit of time on a docker-compose config for launching everything, I need to come back to that. |
Yeah, I think we can close this. |
So following the instructions, it says to edit the
storm.yaml
file and add instorm.zookeeper.servers
andnimbus.host
.So in a perfect world here is how this would work:
mesos.master.url
attr if that isn't specified.Or is it preferred to run this under something like marathon?
The text was updated successfully, but these errors were encountered: