If riak_kv is not ready, and riak_kv_replrtq_snk starts work it will fetch from queues on the remote cluster, but not be able to put those changes into this cluster.
This defers the prompting of work on startup until after riak_kv is ready. The riak_kv_replrtq_peer can also prompt work - so this too is delayed until riak_kv has started.
The riak_kv_ttaaefs_manager will not function correctly without riak_kv being started, so this also has startup deferred should riak_kv not be ready after the initial startup timeout.
If riak_kv is not ready, and
riak_kv_replrtq_snk
starts work it will fetch from queues on the remote cluster, but not be able to put those changes into this cluster.This defers the prompting of work on startup until after riak_kv is ready. The
riak_kv_replrtq_peer
can also prompt work - so this too is delayed until riak_kv has started.The
riak_kv_ttaaefs_manager
will not function correctly without riak_kv being started, so this also has startup deferred should riak_kv not be ready after the initial startup timeout.