diff options
| author | Daniil Fedotov <hairyhum@gmail.com> | 2018-04-18 16:02:26 +0100 |
|---|---|---|
| committer | Daniil Fedotov <hairyhum@gmail.com> | 2018-04-18 16:24:20 +0100 |
| commit | 5f06ff470fcd4e395f4c66da4376f1f660172451 (patch) | |
| tree | f2cb00261c77713f9a83588440cb725e048721dd /test | |
| parent | 3b4af50b8886cf11a2d39b2cd0d92c0745dc9d84 (diff) | |
| download | rabbitmq-server-git-5f06ff470fcd4e395f4c66da4376f1f660172451.tar.gz | |
Introduce a new policy: ha-promote-on-failure (always by default)
This new policy controls if unsynchronised slaves should be promoted
after master crash. If set to `when-synced`, unsynchronised slaves
will not be promoted, keeping the state of the queue, but making it
unavailable until master node returns.
This change is supposed to make the cluster shutdown safier,
because queues can fail or be killed on shutdown.
The queues without master will be available from the management UI
and can be deleted and redeclared, but will not automatically loose
messages.
Trying to declare or passively declare the queue will result in a
timeout error. Same way as if the master was gracefully stopped with
ha-promote-on-shutdown: when-synced
[#156811690]
Diffstat (limited to 'test')
0 files changed, 0 insertions, 0 deletions
