diff options
| author | Alexandru Scvortov <alexandru@rabbitmq.com> | 2011-07-20 11:07:51 +0100 |
|---|---|---|
| committer | Alexandru Scvortov <alexandru@rabbitmq.com> | 2011-07-20 11:07:51 +0100 |
| commit | 10c46203e5ae4cfb4cb1a36f2a73a54573a3870c (patch) | |
| tree | 623423a3c44fca9231e2332239800a5fb5ceb816 /src/bpqueue.erl | |
| parent | 029750c33d69321061cd16f780fa5027b6aa6868 (diff) | |
| download | rabbitmq-server-git-10c46203e5ae4cfb4cb1a36f2a73a54573a3870c.tar.gz | |
enable disc-less nodes
The main trouble with this is
mnesia:change_config(extra_db_nodes,...). If the current node doesn't
have a schema with all the tables created, it will get it from one of
the nodes it connects to. This is a problem if we're a disc node and
they're a ram node or vice versa. So, after we get the tables from
the other node and wait_for_remote_tables, we assert that their
storage location is correct and change it if not. If the other node
is disc and we are ram, this unfortunately means that the tables are
first written to disc and then converted to ram, but since this is a
one-off operation during startup, it shouldn't be a problem.
Diffstat (limited to 'src/bpqueue.erl')
0 files changed, 0 insertions, 0 deletions