summaryrefslogtreecommitdiff
path: root/src/rabbit_upgrade.erl
diff options
context:
space:
mode:
authorSimon MacMullen <simon@rabbitmq.com>2012-09-18 15:59:46 +0100
committerSimon MacMullen <simon@rabbitmq.com>2012-09-18 15:59:46 +0100
commitb46488c91b5a9ada37b3889f630e8d0b66bbc8c2 (patch)
tree1564f30cccfbf73a300e0b7588fa51e970ca1ac7 /src/rabbit_upgrade.erl
parent1b1e490ea0c0f0bddbc8ea5f5c91d0df895f691b (diff)
downloadrabbitmq-server-b46488c91b5a9ada37b3889f630e8d0b66bbc8c2.tar.gz
Oops
Diffstat (limited to 'src/rabbit_upgrade.erl')
-rw-r--r--src/rabbit_upgrade.erl4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/rabbit_upgrade.erl b/src/rabbit_upgrade.erl
index 2b591c2e..9c54eb72 100644
--- a/src/rabbit_upgrade.erl
+++ b/src/rabbit_upgrade.erl
@@ -66,11 +66,11 @@
%% into the boot process by prelaunch before the mnesia application is
%% started. By the time Mnesia is started the upgrades have happened
%% (on the primary), or Mnesia has been reset (on the secondary) and
-%% rabbit_mnesia:init_db/3 can then make the node rejoin the cluster
+%% rabbit_mnesia:init_db_unchecked/2 can then make the node rejoin the cluster
%% in the normal way.
%%
%% The non-mnesia upgrades are then triggered by
-%% rabbit_mnesia:init_db/3. Of course, it's possible for a given
+%% rabbit_mnesia:init_db_unchecked/2. Of course, it's possible for a given
%% upgrade process to only require Mnesia upgrades, or only require
%% non-Mnesia upgrades. In the latter case no Mnesia resets and
%% reclusterings occur.