summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #2389 from ↵Michael Klishin2020-06-241-0/+28
|\ | | | | | | | | rabbitmq/restore-dist-port-configuration-for-windows-service scripts/rabbitmq-service.bat: Configure Erlang distribution port
| * scripts/rabbitmq-service.bat: Configure Erlang distribution portJean-Sébastien Pédron2020-06-191-0/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As said in the comment, this is normally done at runtime now (see rabbitmq/rabbitmq-server#2180). However, we must configure the distribution on the command line specifically for the Windows service. Until this patch, the distribution was enabled with the correct nodename, but the TCP port configuration was not set. This caused a regression because the selected TCP port was random instead of the expected default of 25672. This patch restores the previous behavior. Fixes rabbitmq/rabbitmq-server#2387.
* | Update erlang.mkJean-Sébastien Pédron2020-06-231-3/+71
|/
* Merge pull request #2378 from rabbitmq/load-conf-before-erlang-dist-setupJean-Sébastien Pédron2020-06-101-4/+4
|\ | | | | rabbit_prelaunch: Load configuration before Erlang dist. is started
| * rabbit_prelaunch: Load configuration before Erlang dist. is startedJean-Sébastien Pédron2020-06-101-4/+4
|/ | | | | | | | The reason is that kernel's `net_ticktime` can be configured in the Cuttlefish or Erlang configuration files. If we start the distribution first, then the configuration parameter is ignored. Fixes #2377.
* Merge pull request #2375 from rabbitmq/rabbit-fifo-int-test-stabilityPhilip Kuryloski2020-06-101-10/+14
|\ | | | | Attempt to increase rabbit_fifo_int_SUITE stability
| * Attempt to increase rabbit_fifo_int_SUITE stabilityPhilip Kuryloski2020-06-091-10/+14
| | | | | | | | | | Wait for messages to have been enqueued before proceeding with the body of the test case
* | Merge pull request #2374 from rabbitmq/metrics-suite-test-stabilityPhilip Kuryloski2020-06-101-3/+7
|\ \ | | | | | | Make connection_metric_idemp_test example rather than property based
| * | Replace connection_metric_idemp_test with specific casesPhilip Kuryloski2020-06-091-3/+7
| |/ | | | | | | | | | | | | | | rather than a property based test. The property test flakes occassionally, and without consistent input values. Idempotency should be properly demonstrated with 2 or more attempts at the action anyway.
* | Merge pull request #2376 from rabbitmq/simple-ha-test-stabilityPhilip Kuryloski2020-06-101-0/+16
|\ \ | | | | | | Stricter setup in the confirms_survive_* tests
| * | Stricter setup in the confirms_survive_* testsPhilip Kuryloski2020-06-091-0/+16
| |/ | | | | | | Wait until at least one message has been confirmed before triggering the survivable change
* | rabbit_prelaunch_conf: Style fixesJean-Sébastien Pédron2020-06-091-15/+20
| | | | | | | | Things like staying in the 80-column limit and spaces around '='.
* | More logging for boot time definition importMichael Klishin2020-06-091-0/+1
| | | | | | | | References #2368, #2373, rabbitmq/rabbitmq-management#818.
* | Don't try to load management.load_definitions in the coreMichael Klishin2020-06-091-11/+3
| | | | | | | | | | | | See #2368 comments for the background. References #2368, #2373.
* | Merge pull request #2373 from rabbitmq/revert-2368-lrb-fix-definition-importMichael Klishin2020-06-091-6/+1
|\ \ | |/ |/| Revert "Ensure rabbitmq_management is loaded"
| * Revert "Ensure rabbitmq_management is loaded"Michael Klishin2020-06-091-6/+1
|/
* Bump Recon to 2.5.1Michael Klishin2020-06-091-2/+2
| | | | | | for Erlang 23 compatibility of 'rabbitmq-diagnostics observer' References zhongwencool/observer_cli#68.
* Merge pull request #2371 from twjs76/support_paths_with_bracketsLuke Bakken2020-06-081-2/+2
|\ | | | | Support RABBITMQ_HOME paths containing brackets on windows
| * Support RABBITMQ_HOME paths containing brackets on windowsThomas Speckert2020-06-081-2/+2
|/ | | | | | | | | | If the environment variable RABBITMQ_HOME contained a path with either '(' or ')' (for example, a path under C:\Program Files (x86)\), then the script would unexpectedly exit with the error '\some\path was unexpected at this time'. This was caused by the parenthesis being interpreted as part of the batch 'if/else'. Adding quotes around the arguments to the SET command fixes the problem.
* Merge pull request #2368 from rabbitmq/lrb-fix-definition-importMichael Klishin2020-06-061-1/+6
|\ | | | | Ensure rabbitmq_management is loaded
| * Ensure rabbitmq_management is loadedLuke Bakken2020-06-051-1/+6
|/ | | | | | | | | | | This ensures that `rabbitmq_management` settings are available at this point in time. If the plugin is not available, this step is skipped because the application can not be loaded. To test: ``` RABBITMQ_SERVER_ADDITIONAL_ERL_ARGS='-rabbitmq_management load_definitions "/tmp/defs.json"' ./sbin/rabbitmq-server ```
* Merge pull request #2366 from rabbitmq/rabbitmq-cli-426Michael Klishin2020-06-052-2/+6
|\ | | | | Deprecate 'ctl node_health_check'
| * Update rabbitmqctl(8) man pageMichael Klishin2020-06-051-2/+4
| |
| * Deprecate 'ctl node_health_check'Michael Klishin2020-06-051-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | * It requires a fully booted node, so not generally suitable for a Kubernetes readiness probe. * It can produce false positives * It is too intrusive and CPU-intensive to use at scale * Most operators do not understand what it really does and when they learn about it, consider it to be too opinionated and intrusive Time for the One True Health Check™ to retire from duty. Part of rabbitmq/rabbitmq-cli#426
* | rabbit: Use `rabbit_prelaunch` to get contextJean-Sébastien Pédron2020-06-041-2/+2
| | | | | | | | | | | | Before this patch, we were using `rabbit_env` directly which computed the environment again. In the end, we would compute the environment four times instead of just once.
* | rabbitmq-defaults.bat: Allow to override `$CONF_ENV_FILE`Jean-Sébastien Pédron2020-06-041-1/+5
|/ | | | It is already possible on Unix.
* Merge pull request #2364 from rabbitmq/rabbitmq-server-2363Michael Klishin2020-06-043-101/+278
|\ | | | | Improves logging for user and permission-related management functions
| * Log a message when 'ctl set_policy' succeedsMichael Klishin2020-06-041-6/+9
| | | | | | | | Part of rabbitmq/rabbitmq-server#2363
| * Improve logging of 'ctl authenticate_user' failuresMichael Klishin2020-06-041-0/+1
| | | | | | | | | | | | | | At debug level only since this code path is used by client connections and authentication failures for are already visibly logged as errors. Part of rabbitmq/rabbitmq-server#2363
| * Improve reporting of 'ctl change_password' failuresMichael Klishin2020-06-041-10/+23
| | | | | | | | Part of rabbitmq/rabbitmq-server#2363
| * Improve reporting of 'ctl set_user_tags' failuresMichael Klishin2020-06-041-8/+20
| | | | | | | | Part of rabbitmq/rabbitmq-server#2363
| * Improve reporting of 'ctl add_user' and 'ctl delete_user' failuresMichael Klishin2020-06-041-11/+37
| | | | | | | | Part of rabbitmq/rabbitmq-server#2363
| * Improve reporting of 'ctl clear_topic_permissions' failuresMichael Klishin2020-06-041-10/+56
| | | | | | | | Part of rabbitmq/rabbitmq-server#2363
| * CosmeticsMichael Klishin2020-06-041-10/+10
| |
| * CosmeticsMichael Klishin2020-06-041-2/+2
| |
| * Improve reporting of 'ctl clear_permissions' failuresMichael Klishin2020-06-041-27/+51
| | | | | | | | Part of rabbitmq/rabbitmq-server#2363
| * Improve reporting of 'ctl set_topic_permissions' failuresMichael Klishin2020-06-041-32/+60
| | | | | | | | Part of rabbitmq/rabbitmq-server#2363
| * Improve reporting of 'ctl set_permissions' failuresMichael Klishin2020-06-041-26/+50
| | | | | | | | Part of rabbitmq/rabbitmq-server#2363
* | Merge pull request #2365 from rabbitmq/simple_ha-test-stabilityPhilip Kuryloski2020-06-041-5/+16
|\ \ | |/ |/| Stricter test setup for simple_ha_SUITE
| * Attempt to increase stability of simple_ha_SUITEPhilip Kuryloski2020-06-041-5/+16
| | | | | | | | Wait for an ack on the first message sent to the queue before proceeding with the test, since we assert on that message in the tail of the test.
* | Merge pull request #2362 from rabbitmq/rabbitmq_server_2324Michael Klishin2020-06-034-1/+22
|\ \ | | | | | | Use the newly defined MSG_STORE_WORKER_WAIT for rabbit_msg_store
| * | Message store settings we already have use the "msg_store" prefixMichael Klishin2020-06-033-3/+4
| | |
| * | Expose new message store worker timeout setting to rabbitmq.confMichael Klishin2020-06-032-0/+20
| | | | | | | | | | | | Part of #2324.
| * | Use the newly defined MSG_STORE_WORKER_WAIT for rabbit_msg_storePhilip Kuryloski2020-06-021-1/+1
| |/ | | | | | | In order raise the default timeout for gracefully shutting down message stores, without affecting a larger set of supervisors, introduce a specific macro for this case
* | Test cases for short peer discovery aliasesMichael Klishin2020-06-031-1/+25
| |
* | Merge pull request #2359 from rabbitmq/rabbitmq-server-2317-part-1Michael Klishin2020-06-022-3/+11
|\ \ | |/ |/| rabbit_mnesia:is_virgin_node/0: take overridden Ra data directory into account
| * rabbit_mnesia:is_virgin_node/0: take overridden Ra data directory into accountMichael Klishin2020-06-022-3/+11
|/ | | | | | | as well as the default location because it can exist for various reasons early on node startup. Part of rabbitmq/rabbitmq-server#2317
* Merge pull request #2355 from rabbitmq/rabbitmq-server-2354Michael Klishin2020-06-013-1/+21
|\ | | | | Introduce raft.data_dir to new style configuration schema
| * Expose Ra data directory in rabbit:status/0Michael Klishin2020-05-301-1/+2
| |
| * Introduce raft.data_dir to new style configuration schemaMichael Klishin2020-05-292-0/+19
| | | | | | | | | | | | | | | | | | | | | | | | As an experimental feature for now. To be sure that this value has the desired effect we may have to tweak the way Ra dependency is started. Some ealy tests suggest this works as expected already. Per discussion with @kjnilsson. Closes #2354.