The riak admin reip command in the riak-admin script depends on two node_package env.sh scripts, that no longer exist:
The reip command also depends on the check_config command populating the $CONFIG_ARGS.
As this command normally requires on the node being down, it isn't obvious that it can be safely replaced by starting the node and running riak_kv_console:reip/1 from remote_console (and as this would start the ring manager, and potentially gossip this, it might not be safe).
@Bob-The-Marauder - have you guys hit this, and if so do you have a workaround?
Sadly riak_test has no tests for this.
The
riak admin reipcommand in the riak-admin script depends on two node_package env.sh scripts, that no longer exist:The reip command also depends on the
check_configcommand populating the $CONFIG_ARGS.As this command normally requires on the node being down, it isn't obvious that it can be safely replaced by starting the node and running
riak_kv_console:reip/1from remote_console (and as this would start the ring manager, and potentially gossip this, it might not be safe).@Bob-The-Marauder - have you guys hit this, and if so do you have a workaround?
Sadly riak_test has no tests for this.