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

missing riak_core modules on develop build #578

Closed
jrwest opened this issue Jul 28, 2014 · 7 comments
Closed

missing riak_core modules on develop build #578

jrwest opened this issue Jul 28, 2014 · 7 comments
Assignees

Comments

@jrwest
Copy link
Contributor

jrwest commented Jul 28, 2014

trying to reproduce an issue on develop branch led to the following errors. need to investigate further but I don't have a moment right now so filing here for later.

$ for d in dev/dev{2,3,4,5}; do $d/bin/riak-admin cluster join dev1@127.0.0.1; done 
Success: staged join request for 'dev2@127.0.0.1' to 'dev1@127.0.0.1'
Success: staged join request for 'dev3@127.0.0.1' to 'dev1@127.0.0.1'
Success: staged join request for 'dev4@127.0.0.1' to 'dev1@127.0.0.1'
Success: staged join request for 'dev5@127.0.0.1' to 'dev1@127.0.0.1'
$ dev/dev1/bin/riak-admin cluster plan 
RPC to 'dev1@127.0.0.1' failed: {'EXIT',
                                 {undef,
                                  [{riak_core_console,print_staged,[],[]},
                                   {rpc,'-handle_call_call/6-fun-0-',5,
                                    [{file,"rpc.erl"},{line,205}]}]}}
$ dev/dev1/bin/riak-admin cluster commit 
RPC to 'dev1@127.0.0.1' failed: {'EXIT',
                                 {undef,
                                  [{riak_core_console,commit_staged,[],[]},
                                   {rpc,'-handle_call_call/6-fun-0-',5,
                                    [{file,"rpc.erl"},{line,205}]}]}}

@jrwest jrwest self-assigned this Jul 28, 2014
@jrwest jrwest changed the title missing riak_core_modules on develop build missing riak_core modules on develop build Jul 28, 2014
@jrwest
Copy link
Contributor Author

jrwest commented Jul 28, 2014

with make locked-deps ran before make devrel the build works fine. @jaredmorrow any off-the-top-of-your-head ideas before I dig a bit more?

@jaredmorrow
Copy link
Contributor

Only thing I can think of is something getting left out of the toplevel reltool.config and modules aren't getting added to the rel as expected, but if core is doing the right thing, that shouldn't be a problem.

@kellymclaughlin
Copy link
Contributor

I have reproduced the problem and it can be attributed to the merging of basho/node_package#155. There are several calls in riak_core_console that do not need to accept any input parameters, but accept just the empty list due to the exact limitation described in the node_package PR. I'll go through and convert all those console functions appropriately.

@jrwest jrwest assigned kellymclaughlin and unassigned jrwest Jul 28, 2014
@jaredmorrow
Copy link
Contributor

FYI, so this won't affect 2.0 right now, since that node_package PR wasn't included.

@jrwest
Copy link
Contributor Author

jrwest commented Jul 28, 2014

agreed. on the riak-2.0.0rc1 tag I have confirmed that everything builds fine.

@kellymclaughlin
Copy link
Contributor

After looking more into this and thinking about what it would take to make this work in mixed cluster scenarios up until the point where people are no longer upgrading to some future version from 2.0 (i.e. a few years down the road) I am not sure it is worth the effort. I think I will just open a PR to revert my node_package change and handle the no parameter rpc case for the specific scenrio in riak_cs I was working on the same way it is handled in riak-admin.

@kellymclaughlin
Copy link
Contributor

basho/node_package#156

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants