summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNick Vatamaniuc <vatamane@apache.org>2018-09-26 13:08:45 -0400
committerNick Vatamaniuc <nickva@users.noreply.github.com>2018-10-02 12:15:17 -0400
commitabb2a86545d311884fe3256a30c4f7d75e0b26ef (patch)
tree1ccb229aa9b0d7939aa5be56dc7b23fe37287468
parentb3549149f1a871974cff3c9a260c217eb57ec849 (diff)
downloadcouchdb-abb2a86545d311884fe3256a30c4f7d75e0b26ef.tar.gz
Make sure to start per-node rexi servers right away
This ensures they will be ready to process requests as soon as the application starts up. This should make the service available sooner and should help tests which setup and tear down the services repeatedly, where it would avoid an annoying retry-until-ready loop. Per-node servers/buffers are started in the init method of the monitors. There is not chance of deadlock there because per-node supervisors are started before the monitors. Issue #1625
-rw-r--r--src/rexi/src/rexi_server_mon.erl2
1 files changed, 2 insertions, 0 deletions
diff --git a/src/rexi/src/rexi_server_mon.erl b/src/rexi/src/rexi_server_mon.erl
index 86fecaff6..cfe1144ce 100644
--- a/src/rexi/src/rexi_server_mon.erl
+++ b/src/rexi/src/rexi_server_mon.erl
@@ -68,6 +68,8 @@ cluster_stable(Server) ->
init(ChildMod) ->
{ok, _Mem3Cluster} = mem3_cluster:start_link(?MODULE, self(),
?CLUSTER_STABILITY_PERIOD_SEC, ?CLUSTER_STABILITY_PERIOD_SEC),
+ start_servers(ChildMod),
+ couch_log:notice("~s : started servers", [ChildMod]),
{ok, ChildMod}.