diff options
| author | Matthew Sackman <matthew@rabbitmq.com> | 2011-03-23 18:06:16 +0000 |
|---|---|---|
| committer | Matthew Sackman <matthew@rabbitmq.com> | 2011-03-23 18:06:16 +0000 |
| commit | 5d51177b297d5425741b808fb6f78a2712a0376e (patch) | |
| tree | 1591d809c0cdbf85244e18d120b27d4b70235c64 | |
| parent | fec6c5e2279bd726b27c76bc0b464c53a7f5525a (diff) | |
| download | rabbitmq-server-5d51177b297d5425741b808fb6f78a2712a0376e.tar.gz | |
cough
| -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 5ec08330..a2abb1e5 100644 --- a/src/rabbit_upgrade.erl +++ b/src/rabbit_upgrade.erl @@ -64,11 +64,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/2 can then make the node rejoin the cluster +%% rabbit_mnesia:init_db/3 can then make the node rejoin the cluster %% in the normal way. %% %% The non-mnesia upgrades are then triggered by -%% rabbit_mnesia:init_db/2. Of course, it's possible for a given +%% rabbit_mnesia:init_db/3. 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. |