summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorAlexandru Scvortov <alexandru@rabbitmq.com>2011-07-20 12:42:37 +0100
committerAlexandru Scvortov <alexandru@rabbitmq.com>2011-07-20 12:42:37 +0100
commit86569edf5653a90cbc1b1a8612544fd37551d1a8 (patch)
tree9cc34a45f108d007075b43b0691ffd1bc727e8b8 /include
parent381213af0b7b3cc3a3d898fdf77cfacf19574875 (diff)
downloadrabbitmq-server-git-86569edf5653a90cbc1b1a8612544fd37551d1a8.tar.gz
test that disc nodes are actually disc nodes
The tests used to be slightly wrong. They'd expect: rabbitmqctl cluster to create a cluster with a single ram node. It didn't, instead, it created a cluster with a single disc node. Since we weren't actually checking the resulting node type, everything went along fine. Assert_tables_copy_type is complicated by all the cases it has to handle, namely converting disc -> ram and ram -> disc. For disc -> ram, we first need to convert all the tables to ram, then, we need to convert the schema (converting it before fails with "Disc resident tables"). For ram -> disc, we first need to convert the schema, otherwise, all the table conversions will fail with 'has_no_disc'. Regarding an earlier commit, using mensia:system_info(use_dir) to check if we have a disc node is wrong because we create the directory for the message_store anyway.
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions