summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Check exclusive owner before durable argumentLuke Bakken2019-02-181-7/+7
| | | | Fixes #1887
* Merge pull request #1878 from rabbitmq/rabbitmq-server-1873-binding-recoveryMichael Klishin2019-02-174-15/+23
|\ | | | | Recover bindings for all durable queues including failed to recover.
| * Merge branch 'master' into rabbitmq-server-1873-binding-recoveryMichael Klishin2019-02-1612-144/+80
| |\ | |/ |/|
* | Merge pull request #1884 from rabbitmq/allow_binding_if_tables_inconsistentMichael Klishin2019-02-161-15/+13
|\ \ | | | | | | Do not fail on bind/unbind operations if the binding records are inconsistent.
| * | Revert error handling removal for backwards compatibility.Daniil Fedotov2019-02-151-0/+5
| | | | | | | | | | | | Older versions still can return binding_not_found error.
| * | Do not fail on bind/unbind operations if the binding records are inconsistent.Daniil Fedotov2019-02-142-20/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | If there is a record for the rabbit_durable_route table but no record for rabbit_route table, the binding operations should still proceed to create/remove bindings. This will allow the clients to fix data inconsistency that server did not fix during recovery. [#163952284]
* | | Filter duplicate default exchange binding in ↵Michael Klishin2019-02-161-4/+7
|/ / | | | | | | | | | | | | | | | | | | `rabbit_binding:list_for_destination/1` Follow-up to #1721. Even though the default exchange bindings are deleted at schema migration time, this filtering improves backwards compatibility for mixed version clusters.
* | Merge pull request #1882 from rabbitmq/rabbitmq-server_conf_exampleMichael Klishin2019-02-141-3/+3
|\ \ | | | | | | Remove inet_dist_listen_* configuration
| * | Remove inet_dist_listen_* configurationGabriele2019-02-141-3/+3
|/ / | | | | | | part of https://github.com/rabbitmq/rabbitmq-server/pull/1881
* | Remove inet_dist_listen_min / max from ini schema since they do not workLuke Bakken2019-02-143-24/+1
| | | | | | | | (cherry picked from commit 260098ecd053ec10e407ec65ac2a17512f4d4455)
* | Assing RABBITMQ_CONFIG_ARG_FILE variableGabriele2019-02-141-0/+1
| | | | | | | | | | | | The rabbit_prelaunch module can read the os:getenv(RABBITMQ_CONFIG_ARG_FILE) correctly (cherry picked from commit 68d52f96bd14d79f9cfd8789637d935182365edc)
* | Use the new feature flags helper in `rabbit_ct_broker_helpers`Jean-Sébastien Pédron2019-02-136-82/+33
| | | | | | | | | | | | It simplifies the test of feature flags support. While here, update the `queue_parallel` testsuite to use it.
* | dynamic_ha suite: remove a racy assertionMichael Klishin2019-02-131-2/+2
| | | | | | | | | | | | | | | | | | | | | | Asserting that a process on a remote node is down at this very moment is inherently racy and opportunistic. rabbit_ct_broker_helpers:force_vhost_failure/2 will retry up to 10 times to make sure that the top vhost supervision tree process did go down. That is good enough. Per discussion with @kjnilsson.
* | CompileMichael Klishin2019-02-131-1/+1
| |
* | An attempt to make dynamic_ha suite more resilientMichael Klishin2019-02-131-15/+21
| |
| * Merge branch 'master' into rabbitmq-server-1873-binding-recoveryMichael Klishin2019-02-1354-124/+112
| |\ | |/ |/|
* | Merge pull request #1875 from rabbitmq/fix-more-dialyzerMichael Klishin2019-02-1314-49/+37
|\ \ | | | | | | Fix more dialyzer warnings
| * \ Merge branch 'master' into fix-more-dialyzerMichael Klishin2019-02-1247-740/+871
| |\ \ | |/ / |/| |
* | | Merge branch 'jsoref-spelling'Michael Klishin2019-02-1245-75/+75
|\ \ \
| * \ \ Merge branch 'spelling' of https://github.com/jsoref/rabbitmq-server into ↵Michael Klishin2019-02-1245-75/+75
| |\ \ \ |/ / / / | | | | | | | | jsoref-spelling
| * | | spelling: withinJosh Soref2019-02-121-1/+1
| | | |
| * | | spelling: variableJosh Soref2019-02-121-1/+1
| | | |
| * | | spelling: theoreticallyJosh Soref2019-02-121-1/+1
| | | |
| * | | spelling: synchronousJosh Soref2019-02-121-4/+4
| | | |
| * | | spelling: supportJosh Soref2019-02-122-2/+2
| | | |
| * | | spelling: specifyingJosh Soref2019-02-121-1/+1
| | | |
| * | | spelling: simplifiedJosh Soref2019-02-121-1/+1
| | | |
| * | | spelling: runtimeJosh Soref2019-02-121-1/+1
| | | |
| * | | spelling: rotationJosh Soref2019-02-121-1/+1
| | | |
| * | | spelling: resettingJosh Soref2019-02-121-1/+1
| | | |
| * | | spelling: relevantJosh Soref2019-02-121-1/+1
| | | |
| * | | spelling: registryJosh Soref2019-02-121-1/+1
| | | |
| * | | spelling: refreshJosh Soref2019-02-121-3/+3
| | | |
| * | | spelling: redirectJosh Soref2019-02-121-1/+1
| | | |
| * | | spelling: redeliveredJosh Soref2019-02-121-1/+1
| | | |
| * | | spelling: queuingJosh Soref2019-02-122-2/+2
| | | |
| * | | spelling: protocolJosh Soref2019-02-121-1/+1
| | | |
| * | | spelling: priorityJosh Soref2019-02-121-1/+1
| | | |
| * | | spelling: predicateJosh Soref2019-02-121-1/+1
| | | |
| * | | spelling: possibilitiesJosh Soref2019-02-121-1/+1
| | | |
| * | | spelling: positivesJosh Soref2019-02-121-1/+1
| | | |
| * | | spelling: permutationJosh Soref2019-02-122-2/+2
| | | |
| * | | spelling: overriddenJosh Soref2019-02-125-5/+5
| | | |
| * | | spelling: outputJosh Soref2019-02-121-1/+1
| | | |
| * | | spelling: optimisation (en-GB)Josh Soref2019-02-121-1/+1
| | | |
| * | | spelling: notificationJosh Soref2019-02-121-1/+1
| | | |
| * | | spelling: monitorJosh Soref2019-02-121-1/+1
| | | |
| * | | spelling: maximumJosh Soref2019-02-121-1/+1
| | | |
| * | | spelling: maintenanceJosh Soref2019-02-121-1/+1
| | | |
| * | | spelling: macroJosh Soref2019-02-121-1/+1
| | | |