delta/rabbitmq-server-git.git, branch v3.7.7

(doc) fix typo in mqtt vhost section

2018-06-20T23:19:54+00:00

(cherry picked from commit 28f14e08d10c6d80a8f0b89a33b244578a8e5f9b)

Merge pull request #1622 from rabbitmq/erlang-otp-21-compatibility

2018-06-13T22:37:45+00:00

Erlang/OTP 21 compatibility

Be more defensive about what output rabbitmqctl eval produces here

2018-06-13T15:56:21+00:00

OTP 21 has a new logging subsystem and extra logging added to the kernel app
to accompany the asynchronous automatic node connection feature. This breaks
this eval command that asks the node for some of its effective paths (e.g.
the plugin dir).

Since we know the set of lines we are interested in, we can filter out
everything else.

Pair: @dumbbell.

Part of #1616.

[#157964874]

(cherry picked from commit dae785ab345c4102bf5ddf6a1a733025a84191fd)

Compile Erlang/OTP 21

2018-06-13T15:56:21+00:00

OTP 21 deprecated erlang:get_stacktrace/0 in favor of a new
try/catch syntax. Unfortunately that's not realistic for projects
that support multiple Erlang versions (like us) until OTP 21 can be
the minimum version requirement. In order to compile we have to ignore
the warning. The broad compiler option seems to be the most common
way to support compilation on multiple OTP versions with warnings_as_errors.

[#157964874]

(cherry picked from commit e3b2830647caa29add5df77438335294baa99e2d)

Update rabbitmq-components.mk

2018-06-13T15:41:29+00:00

Use rabbit_data_coercion:to_list/1 to coerce discovered node name to a string

2018-06-07T01:13:46+00:00

Previous implementation breaks on OTP 21.

[#157964874]

(cherry picked from commit da011eb94ed79463daf912756dd866f2d777c0c3)
(cherry picked from commit ac50a38ea8ef9fcdcaf49aca5c711ccdd4ad3c1f)

Don't await for error_logger handlers to initialise

2018-06-07T01:13:36+00:00

It will never be started on OTP 21.

The problem this piece of code originally was added to solve
is not very relevant now that we use Lager. Arguably connection
rate throttling should be enforced elsewhere, be it Ranch or a proxy/load balancer.

In any case, this particular implementation worked around an error_logger
issue that is no longer problematic for us, and eventually won't be problematic
for the entire ecosystem because OTP 21 introduced a completely new logger.

Cherry-picked per discussion with @dumbbell and @lukebakken.

[#157964874]

(cherry picked from commit a54b44fd8d24af90d8df301658fba4775f957bc8)
(cherry picked from commit a210d82f54a133eae167da036302c1c63b3d4d9a)

Minor README updates

2018-06-07T01:12:45+00:00

(cherry picked from commit ed40ab692930349c04d42df370e9b6a5681dd711)

fix default heartbeat in example conf file to 60

2018-06-01T23:27:26+00:00

listed as 600, not the true default of 60

(cherry picked from commit 19337af368b53c85a3f739cbb178a2b33fbb899c)

Use better default memory allocators

2018-06-01T05:28:14+00:00

We have settled on the following configuration for memory
allocators after testing many different combinations:

+MBas ageffcbf +MHas ageffcbf +MBlmbcs 512 +MHlmbcs 512 +MMmcs 30

They reduce the memory usage and help RabbitMQ reclaim memory,
at the cost of a slight decrease in performance due to an
increased number of memory operations.

We need to start Erlang with these values in order to figure
out whether they are supported. The allocator strategies we
recommend were introduced in Erlang/OTP 20.2.3. The values
can be overriden using RABBITMQ_SERVER_ERL_ARGS.

cc @gerhard

(cherry picked from commit ced1c03338dbb0e19a7ceccd1874432d4235e15f)