| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
Part of rabbitmq/rabbitmq-cli#340
|
| |
|
|
|
|
| |
Let the new status command to do the filtering and formatting.
Part of rabbitmq/rabbitmq-cli#340.
|
| | |
|
| |
|
|
|
|
| |
for CLI tools to format them.
References rabbitmq/rabbitmq-cli#340.
|
| |\
| |
| | |
Follow up to #1973 - ensure amq.rabbitmq.log exchange is declared early
|
| | |
| |
| |
| | |
is added or recovered
|
| | |
| |
| |
| | |
Part of #1973
|
| |\ \
| |/
|/| |
Update quorum queue supervisor for memory calculation
|
| | |
| |
| |
| | |
[#161752680]
|
| |\ \
| | |
| | | |
Make sure amq.rabbitmq.log is accessible to client connections
|
| | | | |
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| |
| |
| | |
That is, not an internal exchange.
Closes #1973, references #1456.
[#165243321]
|
| | |
| |
| |
| |
| |
| | |
It is relied on by released 3.7.x versions of rabbitmqctl.
References #1971.
|
| |\ \
| |/
|/| |
Handle connection tracking events in a separate process.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
| |
Connection tracking event handling may involve DB operations and closing of
connections (e.g. for vhost deletion).
Because gen_event handles all events in the same process - this may
cause message accumulation in the rabbit_event process and memory
accumulation.
Connection tracking process will only receive connection tracking
events and all other events will be dropped, freeing the memory.
Follow-up to #1722
[#164353033]
|
| |
|
|
|
|
|
|
|
| |
Before this patch, the migration function waited once 30 seconds then
gave up. This was inconsistent with what the boot process does: wait for
30 seconds, 10 times in a row.
Now, we do the same thing in the `quorum_queue` migration function, so
that it gives up at the same time as the boot process.
|
| |\
| |
| | |
Quorum queue: make membership changes [more] idempotent
|
| |/
|
|
| |
Per discussion with @kjnilsson.
|
| |\
| |
| | |
Cache vhost access requests using client IP address only
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Part of rabbitmq/rabbitmq-auth-backend-cache#20
|
| |\ \
| | |
| | | |
Follow-up to rabbitmq-server#1962
|
| | | | |
|
| | |\ \ |
|
| | | | |
| | | |
| | | |
| | | | |
Fix issues with forward slashes in RABBITMQ_CONFIG_FILE on windows
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
rabbitmq/mnesia_use_ram_schema_on_consistency_check
Mnesia use ram schema on consistency check
|
| | |\ \ \ \ |
|
| | | | | | | |
|
| | | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
By default mnesia uses opt_disk schema location, which will use
a disk schema if there is a directory. This also applies to the
autogenerated directory.
In some cases if the data directory has an autogenerated schema
directory left from previous versions - the node startup will fail.
There is no point in reading a schema on consistency check anyway.
[#164807008]
|
| |\ \ \ \ \
| |_|/ / /
|/| | | | |
Purge stale node state from quorum queues
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When a node is disconnected then removed from the RabbitMQ cluster it is
possibly that quorum queues retain some state for this node. This change
purges any enqueuer or consumer state for pids relating to nodes that
are not in the RabbitMQ cluster.
[#164214265]
|
| |\ \ \ \
| | | | |
| | | | | |
Add a no_return() type spec to silence a Dialyzer warning
|
| |/ / / / |
|
| |\ \ \ \
| |/ / /
|/| | | |
Rabbit fifo bug fixes
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
To test send_msg ordering and ensure there never two active consumers at
once.
[#164691411]
|
| | | | |
| | | |
| | | |
| | | | |
After a down command is processed
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Bugfixes around noconnect consumer handling as well as refactoring to
make these kinds of errors less likely.
[#164691411]
|
| |\ \ \ \
| |_|/ /
|/| | | |
|
| | | | | |
|
| | |\ \ \
|/ / / /
| | | |
| | | | |
https://github.com/masaki-furuta/rabbitmq-server into masaki-furuta-toggle_disk_monitor
|
| | | | |
| | | |
| | | | |
Remove unused default value for enabled.
|
| | | |/
| |/|
| | |
| | |
| | |
| | |
| | | |
To disbale:
rabbitmqctl eval 'rabbit_disk_monitor:set_enabled(false).'
To re-enable:
rabbitmqctl eval 'rabbit_disk_monitor:set_enabled(true).'
|
| |\ \ \
| | | |
| | | | |
URL Cleanup
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This commit updates URLs to prefer the https protocol. Redirects are not followed to avoid accidentally expanding intentionally shortened URLs (i.e. if using a URL shortener).
# Fixed URLs
## Fixed Success
These URLs were switched to an https URL with a 2xx status. While the status was successful, your review is still recommended.
* [ ] http://www.apache.org/licenses/LICENSE-2.0 with 2 occurrences migrated to:
https://www.apache.org/licenses/LICENSE-2.0 ([https](https://www.apache.org/licenses/LICENSE-2.0) result 200).
|
| |\ \ \
| |/ /
|/| | |
Quorum Queues: resend messages if first batch is lost
|
| | |\ \ |
|