config file(s) : /etc/rabbitmq/rabbitmq.configwill show up in the log file .
#example rabbitmq-env.conf file entries #Rename the node NODENAME=bunny@myhost #Config file location and new filename bunnies.config CONFIG_FILE=/etc/rabbitmq/testdir/bunniesMore info on using rabbitmq-env.conf 。
Name |
Default |
Description |
RABBITMQ_NODE_IP_ADDRESS |
the empty string - meaning bind to all network interfaces. 空字符串 -- 表明绑定所有网络接口 |
Change this if you only want to bind to one network interface. 如果你只想要绑定唯一一个网络接口则可以使用该配置进行设置。 |
RABBITMQ_NODE_PORT |
5672 |
|
RABBITMQ_DIST_PORT |
RABBITMQ_NODE_PORT + 20000 |
Port to use for clustering. Ignored if your config file sets inet_dist_listen_min or inet_dist_listen_max 用于集群的端口。如果你在配置文件中设置了 inet_dist_listen_min 或 inet_dist_listen_max 则该配置被忽略 |
RABBITMQ_NODENAME |
Unix*: rabbit@$HOSTNAME Windows: rabbit@%COMPUTERNAME% |
The node name should be unique per erlang-node-and-machine combination. To run multiple nodes, see the clustering guide. 节点名需要在 erlang-node-and-machine 级别上做到唯一。若想要运行多个 node,请参考集群配置。 |
RABBITMQ_SERVICENAME |
Windows Service: RabbitMQ |
The name of the installed service. This will appear in services.msc. |
RABBITMQ_CONSOLE_LOG |
Windows Service: |
Set this variable to new or reuse to redirect console output from the server to a file named %RABBITMQ_SERVICENAME%.debug in the default RABBITMQ_BASE directory. If not set, console output from the server will be discarded (default). new A new file will be created each time the service starts. reuse The file will be overwritten each time the service starts. |
RABBITMQ_CTL_ERL_ARGS |
None |
Parameters for the erl command used when invoking rabbitmqctl. This should be overridden for debugging purposes only. 用于给 rabbtimqctl 提供定制参数。仅在调试目的下使用。 |
RABBITMQ_SERVER_ERL_ARGS |
Unix*: "+K true +A30 +P 1048576 -kernel inet_default_connect_options [{nodelay,true}]" Windows: None |
Standard parameters for the erl command used when invoking the RabbitMQ Server. This should be overridden for debugging purposes only. 在通过 erl 命令启动 RabbitMQ 服务器时使用的标准参数。仅在调试目的下使用。 |
RABBITMQ_SERVER_START_ARGS |
None |
Extra parameters for the erl command used when invoking the RabbitMQ Server. This will not override RABBITMQ_SERVER_ERL_ARGS. 在通过 erl 命令启动 RabbitMQ 服务器时可使用的额外参数。该参数不会覆盖掉 RABBITMQ_SERVER_ERL_ARGS 的内容。 |
Name |
Default |
Description |
HOSTNAME |
Unix, Linux: `env hostname` MacOSX: `env hostname -s` |
The name of the current machine |
COMPUTERNAME |
Windows: localhost |
The name of the current machine |
ERLANG_SERVICE_MANAGER_PATH |
Windows Service: %ERLANG_HOME%\erts-x.x.x\bin |
This path is the location of erlsrv.exe, the Erlang service wrapper script. |
[ {mnesia, [{dump_log_write_threshold, 1000}]}, {rabbit, [{tcp_listeners, [5673]}]} ].This example will alter the dump_log_write_threshold for mnesia (increasing from the default of 100), and alter the port RabbitMQ listens on from 5672 to 5673.
Key |
Documentation |
tcp_listeners |
List of ports on which to listen for AMQP connections (without SSL). Can contain integers (meaning "listen on all interfaces") or tuples such as {"127.0.0.1", 5672} to listen on a single interface. Default: [5672] |
ssl_listeners |
As above, for SSL connections. Default: [] |
ssl_options |
SSL configuration. See the SSL documentation. Default: [] |
vm_memory_high_watermark |
Memory threshold at which the flow control is triggered. See the memory-based flow control documentation. Default: 0.4 |
vm_memory_high_watermark_paging_ratio |
Fraction of the high watermark limit at which queues start to page messages out to disc to free up memory. See the memory-based flow control documentation. Default: 0.5 |
disk_free_limit |
Disk free space limit of the partition on which RabbitMQ is storing data. When available disk space falls below this limit, flow control is triggered. The value may be set relative to the total amount of RAM (e.g. {mem_relative, 1.0}). The value may also be set to an integer number of bytes. By default free disk space must exceed 50MB. See the memory-based flow control documentation. Default: 50000000 |
log_levels |
Controls the granularity of logging. The value is a list of log event category and log level pairs. The level can be one of 'none' (no events are logged), 'error' (only errors are logged), 'warning' (only errors and warning are logged), or 'info' (errors, warnings and informational messages are logged). At present there are three categories defined. Other, currently uncategorised, events are always logged. The categories are:
|
frame_max |
Maximum permissible size of a frame (in bytes) to negotiate with clients. Setting to 0 means "unlimited" but will trigger a bug in some QPid clients. Setting a larger value may improve throughput; setting a smaller value may improve latency. Default: 131072 |
channel_max |
Maximum permissible number of channels to negotiate with clients. Setting to 0 means "unlimited". Using more channels increases memory footprint of the broker. Default: 0 |
heartbeat |
Value representing the heartbeat delay, in seconds, that the server sends in the connection.tune frame. If set to 0, heartbeats are disabled. Clients might not follow the server suggestion, see the AMQP reference for more details. Disabling heartbeats might improve performance in situations with a great number of connections, but might lead to connections dropping in the presence of network devices that close inactive connections. Default: 580 |
default_vhost |
Virtual host to create when RabbitMQ creates a new database from scratch. The exchange amq.rabbitmq.log will exist in this virtual host. Default: <<"/">> |
default_user |
User name to create when RabbitMQ creates a new database from scratch. Default: <<"guest">> |
default_pass |
Password for the default user. Default: <<"guest">> |
default_user_tags |
Tags for the default user. Default: [administrator] |
default_permissions |
Permissions to assign to the default user when creating it. Default: [<<".*">>, <<".*">>, <<".*">>] |
loopback_users |
List of users which are only permitted to connect to the broker via a loopback interface (i.e. localhost). If you wish to allow the default guest user to connect remotely, you need to change this to []. Default: [<<"guest">>] |
cluster_nodes |
Set this to cause clustering to happen automatically when a node starts for the very first time. The first element of the tuple is the nodes that the node will try to cluster to. The second element is either disc or ram and determines the node type. Default: {[], disc} |
server_properties |
List of key-value pairs to announce to clients on connection. Default: [] |
collect_statistics |
Statistics collection mode. Primarily relevant for the management plugin. Options are:
Default: none |
collect_statistics_interval |
Statistics collection interval in milliseconds. Primarily relevant for the management plugin. Default: 5000 |
auth_mechanisms |
SASL authentication mechanisms to offer to clients. Default: ['PLAIN', 'AMQPLAIN'] |
auth_backends |
List of authentication / authorisation databases to use. This list can contain names of modules (in which case the same module is used for both authentication and authorisation), or 2-tuples like {ModN, ModZ} in which case ModN is used for authentication and ModZ is used for authorisation. Other databases than rabbit_auth_backend_internal are available through plugins. Default: [rabbit_auth_backend_internal] |
reverse_dns_lookups |
Set to true to have RabbitMQ perform a reverse DNS lookup on client connections, and present that information through rabbitmqctl and the management plugin. Default: false |
delegate_count |
Number of delegate processes to use for intra-cluster communication. On a machine which has a very large number of cores and is also part of a cluster, you may wish to increase this value. Default: 16 |
trace_vhosts |
Used internally by the tracer. You shouldn't change this. Default: [] |
tcp_listen_options |
Default socket options. You probably don't want to change this. Default: [binary, {packet, raw}, {reuseaddr, true}, {backlog, 128}, {nodelay, true}, {exit_on_close, false}] |
hipe_compile |
Set to true to precompile parts of RabbitMQ with the High Performance Erlang compiler. This will increase the message rate that the server can handle, while also increasing startup time. You might see 20-50% better performance at the cost of approximately 1 minute delay at startup. These figures are highly workload- and hardware-dependent. HiPE support may not be compiled into your Erlang installation. If it is not, enabling this option will just cause a warning message to be displayed and startup will proceed as normal. For example, Debian / Ubuntu users will need to install the erlang-base-hipe package. HiPE is not available at all on some platforms, notably including Windows. This option should be considered experimental. If your Erlang VM segfaults, disable this option again. Default: false |
cluster_partition_handling |
How to handle network partitions. One of ignore, pause_minority or autoheal. See the documentation on partitions for more information. Default: ignore |
msg_store_index_module |
Implementation module for queue indexing. You probably don't want to change this. Default: rabbit_msg_store_ets_index |
backing_queue_module |
Implementation module for queue contents. You probably don't want to change this. Default: rabbit_variable_queue |
msg_store_file_size_limit |
Tunable value for the persister. You almost certainly should not change this. Default: 16777216 |
queue_index_max_journal_entries |
Tunable value for the persister. You almost certainly should not change this. Default: 65536 |