diff options
| author | Simon MacMullen <simon@rabbitmq.com> | 2012-09-18 15:59:46 +0100 |
|---|---|---|
| committer | Simon MacMullen <simon@rabbitmq.com> | 2012-09-18 15:59:46 +0100 |
| commit | b2000dae4e222fa0a4c219fcfc04848559d72d0a (patch) | |
| tree | 1564f30cccfbf73a300e0b7588fa51e970ca1ac7 | |
| parent | a85d916b3444174f4fe1f43e61a65868728812db (diff) | |
| download | rabbitmq-server-git-b2000dae4e222fa0a4c219fcfc04848559d72d0a.tar.gz | |
Oops
| -rw-r--r-- | src/rabbit_upgrade.erl | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/rabbit_upgrade.erl b/src/rabbit_upgrade.erl index 2b591c2ed4..9c54eb7247 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. |