-
Notifications
You must be signed in to change notification settings - Fork 393
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
folsom_sup already started as dep [JIRA: RIAK-1915] #636
Comments
We run folsom as an 'included' application in |
Is there any particular reason to run |
There was a reason. We'd have to look back through the commit messages to find it. We're removing folsom from riak_core soon. So your pain will be temporary. |
I see. Thank you for the response. |
This is making it hard to start other folsom-dependent applications that have normal application dependencies, since I can't see a clean way to tell the dependent application that folsom is "sort of already started". @russelldb, Any ETA on folsom's exit from riak_core? @sumerman, it would be helpful if you briefly described your approach to working around this here. I guess for now I'll work around by forking & removing folsom entirely from the dependent application I'm using. Thanks! |
@emauton we just write metrics code in a way compatible with both basho's and boundary's folsom and using basho's version in production. |
@seancribbs We dont use reltool.config. I just read through all the commit messages, and the code, and I dont see why you cant just have a normal application dependency? |
Recent |
No longer relevant because of Exometer. I think it's safe to close this issue. |
This is still relevant, as |
Trying to push out a demo this week for use of riak_core in our company, but I cant get the workspace to start.
We build an application dependency tree using the release tools, which we flatten into an application boot order. This results in starting folsom, before riak_core. But riak_core_stat_sup later tries to start folsom_sup as its child?
The text was updated successfully, but these errors were encountered: