It turns out that simply not starting search if security is enabled did not play well with the new 'riak-admin security enable' command, because it was decoupled from node startup. Instead, simply disable the endpoint APIs that search exposes if security is enabled, making it more friendly to runtime changes.
Host/port was changed from being a riak_core config to a riak_api config a little while ago. After the default setting for allow_mult (return siblings) was changed, search has been unhappy as it relied on it. This change enforces the old default in search buckets to allow it to exist in this brave new world
… handle_command This is related to basho/riak#407. The old fold_req needs to be caught and upgraded properly, instead of forwarded.