diff options
| author | Simon MacMullen <simon@rabbitmq.com> | 2014-12-10 15:28:42 +0000 |
|---|---|---|
| committer | Simon MacMullen <simon@rabbitmq.com> | 2014-12-10 15:28:42 +0000 |
| commit | b1cad59e2ae0f67bda87eeaaeb3fbc8ed5a14c32 (patch) | |
| tree | 09c3d3f06699b943c10adffc64dcc5b7e81e6694 | |
| parent | 2a44901be5e4a70dad2523555996c5f552a9fbf7 (diff) | |
| download | rabbitmq-server-b1cad59e2ae0f67bda87eeaaeb3fbc8ed5a14c32.tar.gz | |
Minor language corrections.bug26491
| -rw-r--r-- | src/rabbit_autoheal.erl | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/src/rabbit_autoheal.erl b/src/rabbit_autoheal.erl index a4ec86bf..b5d64992 100644 --- a/src/rabbit_autoheal.erl +++ b/src/rabbit_autoheal.erl @@ -199,13 +199,13 @@ winner_finish(Notify) -> %% There is a race in Mnesia causing a starting loser to hang %% forever if another loser stops at the same time: the starting %% node connects to the other node, negotiates the protocol and - %% attemps to acquire a write lock on the schema on the other node. + %% attempts to acquire a write lock on the schema on the other node. %% If the other node stops between the protocol negotiation and lock - %% request, the starting node never gets and answer to its lock + %% request, the starting node never gets an answer to its lock %% request. %% - %% To workaround the problem, we make sure Mnesia is stopped on all - %% loosing nodes before sending the "autoheal_safe_to_start" signal. + %% To work around the problem, we make sure Mnesia is stopped on all + %% losing nodes before sending the "autoheal_safe_to_start" signal. wait_for_mnesia_shutdown(Notify), [{rabbit_outside_app_process, N} ! autoheal_safe_to_start || N <- Notify], not_healing. |