| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
The timeout switch is already a default switch, the command should
not redefine it.
|
| |\ |
|
| | |\
| | |
| | | |
Start/stop windows service using `net` utility instead of `erlsrv`
|
| | | |
| | |
| | |
| | |
| | |
| | | |
`erlsrv` doc suggests to use windows system control tools to control
services. It prints weird error when error is occured
(for example access is denied), so using `net` is prefered.
|
| | | |
| | |
| | |
| | | |
Current management plugin config schema uses `day` instead of
`24hours`: https://github.com/rabbitmq/rabbitmq-management/blob/master/priv/schema/rabbitmq_management.schema.
|
| |\ \ \
| |/ / |
|
| | | | |
|
| |\ \ \
| |/ / |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Like we do in partition_SUITE.
References #1323.
|
| |\ \ \
| |/ /
| | |
| | |
| | | |
Conflicts:
src/rabbit_amqqueue.erl
|
| | |\ \
| | |/
| |/| |
Clean up orphaned exclusive queues
|
| | | | |
|
| | | | |
|
| | | | |
|
| | |/ |
|
| |\ \
| | |
| | | |
Functions to list unresponsive queues
|
| | |\ \
| |/ /
|/| | |
|
| |\ \ \
| | | |
| | | | |
Set ERL_CRASH_DUMP location to rabbitmq log directory
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Lager sink parse-transform allows us to use a fake module name
to select sinks.
It's more convenient that to use a helper function for every module.
Get rif of `rabbit_log_connection` as a sink qualifier.
Qualifiers should be compatible with pre-3.7 qualifiers for plugin developers.
[#149634975]
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If there are no queues to migrate, we should not spend time
starting old message store and doing an empty migration.
Log that there is no migration.
Delete the old message store which can cintain transient queues data.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Upgrade sink is used for logging queue data upgrades.
It should be configured in the start arguments of rabbitmq server.
|
| |\ \ \ \
| |/ / /
|/| | | |
Change the `state` field in vhost info to `cluster_state`.
|
| | |\ \ \
| |/ / /
|/| | | |
|
| |\ \ \ \
| | | | |
| | | | | |
Start queue mirrors after vhost recovery instead of node start
|
| | |\ \ \ \ |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | |\ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Conflicts:
test/dynamic_ha_SUITE.erl
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Vhost supervisors can crash and restart without crashing the
node, so the slave queues on this vhosts should be started
after the vhsot recovery instead of node boot process.
Fixes #1314
[#149484151]
|
| | |_|/ / / /
|/| | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Already started status can be used by CLI tools and should
be returned from `start_vhost` function.
`start_vhost/2` is used in the management API
|
| | | | | | | |
|
| |\ \ \ \ \ \
| |_|/ / / /
|/| | | | | |
Repeat `rabbit_amqqueue:with` operation for a stopped queue.
|
| |/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
A stopped queue can migrate to a synchronized slave if it's mirrored,
so we should retry an operation if it has mirrors to migrate to.
Fixes #1319
|
| | | | | | |
|
| | |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | | |
Vhost supervisor status can be different on different nodes.
Reporting just the current node state doesn't make much sense for
both management and the CLI.
|
| |\ \ \ \
| | | | |
| | | | | |
Check if vhost supervisor is running when starting mirrors
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When a vhost is deleted, both vhost_deleted and vhost_down will
be emitted, resulting in double deletion. rabbit_networking:close_connection/1
therefore can throw an exception about an unknown connection pid.
The handler needs to account for that.
While at it, change log messages to be less alarming and simply
mention vhost shutdown as opposed to "a database failure".
References 7a82b43bf12b737250957081d0b0d84b21b3bf72.
Signed-off-by: Luke Bakken <lbakken@pivotal.io>
|
| | |\ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | | |
Conflicts:
test/vhost_SUITE.erl
|
| |\ \ \ \ \
| |_|/ / /
|/| | | | |
Set queue state to 'stopped' when terminating.
|
| | |\ \ \ \ |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
queue is stopped.
The only operation in `with` which can be performed on a stopped queue
is `delete`. It will call `delete_crashed` based on the `{absent, Q, stopped}`
result from `with`.
|
| | |\ \ \ \ \ |
|