[Why] When the local node joins a remote node, it resets its own data first. This includes the files of the Ra systems (`quorum` and `coordination`). When the CLI is used, that's fine because the `rabbit` app is stopped and thus the Ra systems. However, when this is done as part of peer discovery, the node is booting: the Ra systems were started earlier because they are required to run Khepri. Therefore, the reset deletes files being used. This breaks the Ra systems. [How] The Ra systems are stopped just before the reset (if the join is performed as part of peer discovery) and they are restarted after. |
||
|---|---|---|
| .. | ||
| docs | ||
| include | ||
| priv/schema | ||
| scripts | ||
| src | ||
| test | ||
| .gitignore | ||
| BUILD.bazel | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| INSTALL | ||
| LICENSE | ||
| LICENSE-MPL-RabbitMQ | ||
| Makefile | ||
| README.md | ||
| SECURITY.md | ||
| app.bzl | ||
| bats.bzl | ||
README.md
RabbitMQ Server
RabbitMQ is a feature rich, multi-protocol messaging broker. It supports:
- AMQP 0-9-1
- AMQP 1.0
- MQTT 3.1.1
- STOMP 1.0 through 1.2
Installation
- Installation guides for various platforms
- Kubernetes Cluster Operator
- Changelog
- Releases on GitHub
- Supported and unsupported series
- Supported Erlang versions
Tutorials & Documentation
- RabbitMQ tutorials
- All documentation guides
- CLI tools guide
- Configuration guide
- Client libraries and tools
- Monitoring guide
- Production checklist
- Runnable tutorials
- Documentation source
Getting Help
- RabbitMQ mailing list
- Commercial support from Pivotal for open source RabbitMQ
- Community Slack
#rabbitmqon Freenode
Contributing
See CONTRIBUTING.md and our development process overview.
Questions about contributing, internals and so on are very welcome on the mailing list.
Licensing
RabbitMQ server is licensed under the MPL 2.0.
Building From Source and Packaging
Copyright
(c) 2007-2020 VMware, Inc. or its affiliates.