在AWS上部署时，我遇到了一个与rabbitmq有关的奇怪问题。
当我旋转一个主人，连接一个奴隶，一切顺利，我有两个服务器群集。 当我去添加第二个奴隶的主人，只是挂在join_cluster，并会无限期地等待，而不会引发任何错误。 一旦我停止第一个奴隶，第二个将立即join。 我找不到任何其他人有这个问题或限制奴隶的数量的任何设置。
这是我添加一个条目到主机文件指向一个IP主要在两个从服务器上运行的步骤
rabbitmqctl stop_app rabbitmqctl reset rabbitmqctl join_cluster rabbit@master rabbitmqctl start_app 这是我的rabbitmq.config文件。
[ {rabbit, [ {tcp_listeners, [{{ rabbitmq_amqp_port }}]}, %% SSL listeners are configured in the same fashion as TCP listeners, %% including the option to control the choice of interface. %% %% {ssl_listeners, [5671]}, %% Maximum time for AMQP 0-8/0-9/0-9-1 handshake (after socket connection %% and SSL handshake), in milliseconds. %% %% {handshake_timeout, 10000}, {log_levels, [{connection, info}]}, {loopback_users, [<<"{{ rabbitmq_loopback_user }}">>]}, %% Configuring SSL. %% See http://www.rabbitmq.com/ssl.html for full documentation. %% %% {ssl_options, [{cacertfile, "/path/to/testca/cacert.pem"}, %% {certfile, "/path/to/server/cert.pem"}, %% {keyfile, "/path/to/server/key.pem"}, %% {verify, verify_peer}, %% {fail_if_no_peer_cert, false}]}, {default_vhost, <<"{{ rabbitmq_default_vhost }}">>}, {default_user, <<"{{ rabbitmq_default_user }}">>}, {default_pass, <<"{{ rabbitmq_default_pass }}">>}, {default_permissions, [<<".*">>, <<".*">>, <<".*">>]}, {default_user_tags, [{{ rabbitmq_default_user_tags }}]}, {channel_max, 128}, %% Customising Socket Options. %% %% See (http://www.erlang.org/doc/man/inet.html#setopts-2) for %% further documentation. %% %% {tcp_listen_options, [binary, %% {packet, raw}, %% {reuseaddr, true}, %% {backlog, 128}, %% {nodelay, true}, %% {exit_on_close, false}]}, {vm_memory_high_watermark, {{ rabbitmq_high_watermark }} }, {vm_memory_high_watermark_paging_ratio, {{ rabbitmq_high_watermark_paging }} }, %% Set disk free limit (in bytes). Once free disk space reaches this %% lower bound, a disk alarm will be set - see the documentation %% listed above for more details. %% %% {disk_free_limit, 50000000}, {disk_free_limit, {mem_relative, {{rabbitmq_disk_free_limit}} }} %% Make clustering happen *automatically* at startup - only applied %% to nodes that have just been reset or started for the first time. %% See http://www.rabbitmq.com/clustering.html#auto-config for %% further details. %% %% {cluster_nodes, {['[email protected]'], disc}}, ]} ].
在rabbitmq邮件列表https://groups.google.com/forum/#!topic/rabbitmq-users/Mzb2EhFUD0w上提供完整的书写