summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Nicer feedback.bug26475Simon MacMullen2014-12-091-1/+3
|
* Split out preparation from rename/2, and add comments.Simon MacMullen2014-12-091-29/+77
|
* Various fixes / improvements: with the new scheme multiple renamings will ↵Simon MacMullen2014-12-091-32/+39
| | | | not waork, so check for them. Fix abortive renames (with a copy of the mnesia dir). Ensure we don't talk to any other nodes while backing up / restoring since that inevitably goes wrong. Split up rename/2 a bit and rename a few other things for more clarity.
* Fail clearly if the node specified with '-n' is not a member of the cluster ↵Simon MacMullen2014-12-091-4/+6
| | | | before or after.
* Ensure become(node()) works rather than failing with {node_running, ...}.Simon MacMullen2014-12-091-2/+2
|
* WIP clustererer compatibility: install the fallback and "upgrade" mnesia at ↵Simon MacMullen2014-12-081-13/+14
| | | | rename_cluster_node time, instead of during next boot. This means we need to faff around a bit making sure we do not contact other nodes during the upgrade, but also that on-disk data structures are left in a consistent state for the clusterererer to find them.
* Maybe clearer?Simon MacMullen2014-12-011-1/+1
|
* Add a section to the manual page.Simon MacMullen2014-12-011-0/+35
|
* Swap location of backup and regular config files. A bit less logical, but we ↵Simon MacMullen2014-12-011-4/+4
| | | | need them to be in the right place when starting for big-bang upgrades to work.
* Put all the rename-related temp files in a directory together, and keep ↵Simon MacMullen2014-12-011-13/+21
| | | | copies of the rewritten configs so we can roll back without having to re-edit them.
* Allow argument-pairs to rename_cluster_node to go in any order (and thus ↵Simon MacMullen2014-12-012-23/+46
| | | | allow remote-only renamings). Don't use mnesia:transform_table/3 since it's rather picky about which disk nodes are up.
* Rename againSimon MacMullen2014-11-281-3/+4
|
* And unbreak clusters.Simon MacMullen2014-11-281-0/+1
|
* Detect starting as the old node name after a rename and roll back. Also ↵Simon MacMullen2014-11-282-26/+44
| | | | rename a bit.
* Less io:format, more rabbit_log.Simon MacMullen2014-11-281-7/+6
|
* Improve the chance of not losing a bunch of data.Simon MacMullen2014-11-281-0/+1
|
* OopsSimon MacMullen2014-11-281-1/+1
|
* Rename thingsSimon MacMullen2014-11-282-9/+8
|
* Remove commented out bit, remove pointless RPC (we're in the cluster by that ↵Simon MacMullen2014-11-281-47/+13
| | | | point, we can make Mnesia changes ourselves).
* We are presumably the source of truth now, so make sure we boot.Simon MacMullen2014-11-281-0/+1
|
* Support renaming other remote nodes at the same time, in case we want to do ↵Simon MacMullen2014-11-272-68/+69
| | | | a big bang.
* Don't be so keep to call upgrade_mode/1, it can die in all sorts of ways.Simon MacMullen2014-11-272-30/+35
|
* Rearrange things a bit. We now have something that seems to work.Simon MacMullen2014-11-273-21/+55
| | | | | | | | | | | | | | | | | | | Merging a modified database back into a running cluster seems to be a bit of a non-starter; Mnesia blows up with "Failed to merge schema: Incompatible schema cookies." So instead we do something similar to if we were doing upgrades: we always create the modified backup, but only load it if we are the first node in the cluster to start; if not we reset our mnesia state, resync with the cluster, then tell the cluster to forget our old incarnation and update its queue records for the new one. This also has the advantage that we don't need two rename commands, we just have the local offline one. Which is hopefully nicer operationally. It does mean that we go to the trouble of taking the backup and modifying it only to throw it away if we turn out to be a secondary node, but it should not be too expensive.
* WIP towards rabbitmqctl rename_other_node.Simon MacMullen2014-11-262-1/+29
|
* OopsSimon MacMullen2014-11-261-1/+1
|
* Create a way to mutate pids and use that rather than creating "fake" pids.Simon MacMullen2014-11-263-11/+24
|
* First pass at "rabbitmqctl rename_current_node"Simon MacMullen2014-11-262-3/+139
|
* stable to defaultSimon MacMullen2014-11-2617-187/+507
|\
| * Merge bug26471Simon MacMullen2014-11-2616-178/+493
| |\
| | * Removed tag rabbitmq_v3_4_2Simon MacMullen2014-11-260-0/+0
| | |
| | * Added tag rabbitmq_v3_4_2 for changeset d472925bb786Simon MacMullen2014-11-260-0/+0
| | |
| | * stable to defaultSimon MacMullen2014-11-251-0/+6
| | |\
| | * \ stable to defaultSimon MacMullen2014-11-251-7/+29
| | |\ \
| | * \ \ Merge heads of defaultJean-Sebastien Pedron2014-11-241-4/+4
| | |\ \ \
| | | * \ \ Merge bug26257 (again)Jean-Sebastien Pedron2014-11-244-7/+23
| | | |\ \ \
| | | * | | | When reporting invalid cluster node names, keep configuration orderbug26257Jean-Sebastien Pedron2014-11-241-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | While here, fix an unused variable warning.
| | * | | | | stable to defaultSimon MacMullen2014-11-2416-178/+493
| | |\ \ \ \ \ | | | | |/ / / | | | |/| | |
| | | * | | | Merge bug26257Simon MacMullen2014-11-211-14/+34
| | | |\ \ \ \ | | | | |/ / /
| | | | * | | Detect other invalid 'cluster_nodes' valuesJean-Sebastien Pedron2014-11-211-7/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | In all cases, abort startup with an explanatory message.
| | | | * | | Remove support for the legacy 'cluster_nodes' valuesJean-S?bastien P?dron2014-11-201-13/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Before this change, a list of nodes without the node type was accepted. In this case, the node type was guessed and a warning suggesting how to update the configuration was logged. Now, the node type is mandatory and the RabbitMQ server refuses to start if the node type is unspecified.
| | | * | | | stable to defaultSimon MacMullen2014-11-203-15/+13
| | | |\ \ \ \
| | | * \ \ \ \ stable to defaultSimon MacMullen2014-11-201-1/+13
| | | |\ \ \ \ \
| | | * \ \ \ \ \ stable to defaultSimon MacMullen2014-11-201-1/+7
| | | |\ \ \ \ \ \ | | | | |_|_|/ / / | | | |/| | | | |
| | | * | | | | | stable to defaultSimon MacMullen2014-11-191-0/+5
| | | |\ \ \ \ \ \
| | | * \ \ \ \ \ \ Merge bug26469Simon MacMullen2014-11-1411-96/+201
| | | |\ \ \ \ \ \ \
| | | | * | | | | | | Tweak the APIs again, so that authz plugins aren't expected to create a ↵bug26469Simon MacMullen2014-11-148-71/+120
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | #auth_user record in the first place, just whatever impl they want. Which necessitates seperate login functions for authz and authn, and if we're going to do that we might as well split the behaviours so that we have the possibility of making an authz-only plugin.
| | | | * | | | | | | Rename.Simon MacMullen2014-11-141-2/+2
| | | | | | | | | | |
| | | | * | | | | | | Fix tests.Simon MacMullen2014-11-141-4/+6
| | | | | | | | | | |
| | | | * | | | | | | Never pass the #user{} record into auth backends, they should only see their ↵Simon MacMullen2014-11-137-62/+87
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | own stuff. Get rid of authN_backend, it has little reason for existing. Flatten case of authZ_backend.
| | | | * | | | | | | Cosmetic.Simon MacMullen2014-11-131-31/+30
| | | | | | | | | | |
View Lorry Controller Status