|
|
@@ -15,12 +15,12 @@ emqx_conf_schema {
|
|
|
desc {
|
|
|
en: """Service discovery method for the cluster nodes."""
|
|
|
zh: """集群节点发现方式。可选值为:
|
|
|
-- manual: 手动加入集群<\br>
|
|
|
-- static: 配置静态节点。配置几个固定的节点，新节点通过连接固定节点中的某一个来加入集群。<\br>
|
|
|
-- mcast: 使用 UDP 多播的方式发现节点。<\br>
|
|
|
-- dns: 使用 DNS A 记录的方式发现节点。<\br>
|
|
|
-- etcd: 使用 etcd 发现节点。<\br>
|
|
|
-- k8s: 使用 Kubernetes 发现节点。<\br>
|
|
|
+- manual: 手动加入集群</br>
|
|
|
+- static: 配置静态节点。配置几个固定的节点，新节点通过连接固定节点中的某一个来加入集群。</br>
|
|
|
+- mcast: 使用 UDP 多播的方式发现节点。</br>
|
|
|
+- dns: 使用 DNS A 记录的方式发现节点。</br>
|
|
|
+- etcd: 使用 etcd 发现节点。</br>
|
|
|
+- k8s: 使用 Kubernetes 发现节点。</br>
|
|
|
"""
|
|
|
}
|
|
|
label {
|
|
|
@@ -55,9 +55,9 @@ emqx_conf_schema {
|
|
|
desc {
|
|
|
en: """The Erlang distribution protocol for the cluster."""
|
|
|
zh: """分布式 Erlang 集群协议类型。可选值为:
|
|
|
-- inet_tcp: 使用 IPv4 <\br>
|
|
|
-- inet6_tcp 使用 IPv6 <\br>
|
|
|
-- inet_tls: 使用 TLS，需要与 node.ssl_dist_optfile 配置一起使用。<\br>
|
|
|
+- inet_tcp: 使用 IPv4 </br>
|
|
|
+- inet6_tcp 使用 IPv6 </br>
|
|
|
+- inet_tls: 使用 TLS，需要与 node.ssl_dist_optfile 配置一起使用。</br>
|
|
|
"""
|
|
|
}
|
|
|
label {
|
|
|
@@ -96,7 +96,7 @@ emqx_conf_schema {
|
|
|
|
|
|
cluster_mcast_ports {
|
|
|
desc {
|
|
|
- en: """List of UDP ports used for service discovery.<br/>
|
|
|
+ en: """List of UDP ports used for service discovery.</br>
|
|
|
Note: probe messages are broadcast to all the specified ports.
|
|
|
"""
|
|
|
zh: """指定多播端口。如有多个端口使用逗号 , 分隔。
|
|
|
@@ -231,7 +231,7 @@ Note: probe messages are broadcast to all the specified ports.
|
|
|
desc {
|
|
|
en: """Key prefix used for EMQX service discovery."""
|
|
|
zh: """指定 etcd 路径的前缀。每个节点在 etcd 中都会创建一个路径:
|
|
|
-v2/keys/<prefix>/<cluster.name>/<node.name> <\br>
|
|
|
+v2/keys/<prefix>/<cluster.name>/<node.name> </br>
|
|
|
当 cluster.discovery_strategy 为 etcd 时，此配置项才有效。
|
|
|
"""
|
|
|
}
|
|
|
@@ -300,10 +300,10 @@ It is refreshed automatically, as long as the node is alive.
|
|
|
en: """Address type used for connecting to the discovered nodes."""
|
|
|
zh: """当使用 k8s 方式集群时，address_type 用来从 Kubernetes 接口的应答里获取什么形式的 Host 列表。
|
|
|
指定 cluster.k8s.address_type 为 ip，则将从 Kubernetes 接口中获取 emqx 服务的 IP 地址列表:
|
|
|
-- 172.16.122.31 <\br>
|
|
|
-- 172.16.122.32 <\br>
|
|
|
-- 172.16.122.33 <\br>
|
|
|
-然后与 cluster.k8s.app_name 配置指定的 app name 拼接，得到 emqx 节点列表: <\br>
|
|
|
+- 172.16.122.31 </br>
|
|
|
+- 172.16.122.32 </br>
|
|
|
+- 172.16.122.33 </br>
|
|
|
+然后与 cluster.k8s.app_name 配置指定的 app name 拼接，得到 emqx 节点列表: </br>
|
|
|
- emqx@172.16.122.31
|
|
|
- emqx@172.16.122.32
|
|
|
- emqx@172.16.122.33
|
|
|
@@ -318,10 +318,10 @@ It is refreshed automatically, as long as the node is alive.
|
|
|
cluster_k8s_app_name {
|
|
|
desc {
|
|
|
en: """This parameter should be set to the part of the <code>node.name</code>
|
|
|
-before the '@'.<br/>
|
|
|
+before the '@'.</br>
|
|
|
For example, if the <code>node.name</code> is <code>emqx@127.0.0.1</code>, then this parameter
|
|
|
should be set to <code>emqx</code>."""
|
|
|
- zh: """app_name 用来跟获取的 Host 列表拼接，得到节点列表。<\br>
|
|
|
+ zh: """app_name 用来跟获取的 Host 列表拼接，得到节点列表。</br>
|
|
|
当 cluster.discovery_strategy 为 k8s 时，此配置项才有效。
|
|
|
"""
|
|
|
}
|
|
|
@@ -346,7 +346,7 @@ should be set to <code>emqx</code>."""
|
|
|
|
|
|
cluster_k8s_suffix {
|
|
|
desc {
|
|
|
- en: """Node name suffix.<br/>
|
|
|
+ en: """Node name suffix.</br>
|
|
|
Note: this parameter is only relevant when <code>address_type</code> is <code>dns</code>
|
|
|
or <code>hostname</code>."""
|
|
|
zh: """当使用 k8s 方式并且 cluster.k8s.address_type 指定为 dns 类型时，可设置 emqx 节点名的后缀。
|
|
|
@@ -390,26 +390,26 @@ belong to different clusters from accidentally connecting to each other."""
|
|
|
node_data_dir {
|
|
|
desc {
|
|
|
en: """
|
|
|
-Path to the persistent data directory.<\br>
|
|
|
-Possible auto-created subdirectories are:<\br>
|
|
|
-- `mnesia/<node_name>`: EMQX's built-in database directory.<\br>
|
|
|
-For example, `mnesia/emqx@127.0.0.1`.<\br>
|
|
|
-There should be only one such subdirectory.<\br>
|
|
|
-Meaning, in case the node is to be renamed (to e.g. `emqx@10.0.1.1`),<\br>
|
|
|
-the old dir should be deleted first.<\br>
|
|
|
-- `configs`: Generated configs at boot time, and cluster/local override configs.<\br>
|
|
|
-- `patches`: Hot-patch beam files are to be placed here.<\br>
|
|
|
-- `trace`: Trace log files.<\br>
|
|
|
+Path to the persistent data directory.</br>
|
|
|
+Possible auto-created subdirectories are:</br>
|
|
|
+- `mnesia/<node_name>`: EMQX's built-in database directory.</br>
|
|
|
+For example, `mnesia/emqx@127.0.0.1`.</br>
|
|
|
+There should be only one such subdirectory.</br>
|
|
|
+Meaning, in case the node is to be renamed (to e.g. `emqx@10.0.1.1`),</br>
|
|
|
+the old dir should be deleted first.</br>
|
|
|
+- `configs`: Generated configs at boot time, and cluster/local override configs.</br>
|
|
|
+- `patches`: Hot-patch beam files are to be placed here.</br>
|
|
|
+- `trace`: Trace log files.</br>
|
|
|
|
|
|
**NOTE**: One data dir cannot be shared by two or more EMQX nodes.
|
|
|
"""
|
|
|
zh: """
|
|
|
-节点数据存放目录，可能会自动创建的子目录如下：<\br>
|
|
|
-- `mnesia/<node_name>`。EMQX的内置数据库目录。例如，`mnesia/emqx@127.0.0.1`。<\br>
|
|
|
-如果节点要被重新命名（例如，`emqx@10.0.1.1`）。旧目录应该首先被删除。<\br>
|
|
|
-- `configs`。在启动时生成的配置，以及集群/本地覆盖的配置。<\br>
|
|
|
-- `patches`: 热补丁文件将被放在这里。<\br>
|
|
|
-- `trace`: 日志跟踪文件。<\br>
|
|
|
+节点数据存放目录，可能会自动创建的子目录如下：</br>
|
|
|
+- `mnesia/<node_name>`。EMQX的内置数据库目录。例如，`mnesia/emqx@127.0.0.1`。</br>
|
|
|
+如果节点要被重新命名（例如，`emqx@10.0.1.1`）。旧目录应该首先被删除。</br>
|
|
|
+- `configs`。在启动时生成的配置，以及集群/本地覆盖的配置。</br>
|
|
|
+- `patches`: 热补丁文件将被放在这里。</br>
|
|
|
+- `trace`: 日志跟踪文件。</br>
|
|
|
|
|
|
**注意**: 一个数据dir不能被两个或更多的EMQX节点同时使用。
|
|
|
"""
|
|
|
@@ -530,9 +530,9 @@ significant: later configuration files override the previous ones.
|
|
|
db_backend {
|
|
|
desc {
|
|
|
en: """
|
|
|
-Select the backend for the embedded database.<br/>
|
|
|
+Select the backend for the embedded database.</br>
|
|
|
<code>rlog</code> is the default backend,
|
|
|
-that is suitable for very large clusters.<br/>
|
|
|
+that is suitable for very large clusters.</br>
|
|
|
<code>mnesia</code> is a backend that offers decent performance in small clusters.
|
|
|
"""
|
|
|
zh: """ rlog是默认的数据库，他适用于大规模的集群。
|
|
|
@@ -548,20 +548,20 @@ mnesia是备选数据库，在小集群中提供了很好的性能。
|
|
|
db_role {
|
|
|
desc {
|
|
|
en: """
|
|
|
-Select a node role.<br/>
|
|
|
+Select a node role.</br>
|
|
|
<code>core</code> nodes provide durability of the data, and take care of writes.
|
|
|
-It is recommended to place core nodes in different racks or different availability zones.<br/>
|
|
|
+It is recommended to place core nodes in different racks or different availability zones.</br>
|
|
|
<code>replicant</code> nodes are ephemeral worker nodes. Removing them from the cluster
|
|
|
-doesn't affect database redundancy<br/>
|
|
|
-It is recommended to have more replicant nodes than core nodes.<br/>
|
|
|
+doesn't affect database redundancy</br>
|
|
|
+It is recommended to have more replicant nodes than core nodes.</br>
|
|
|
Note: this parameter only takes effect when the <code>backend</code> is set
|
|
|
to <code>rlog</code>.
|
|
|
"""
|
|
|
zh: """
|
|
|
-选择节点的角色。<br/>
|
|
|
-<code>core</code> 节点提供数据的持久性，并负责写入。建议将核心节点放置在不同的机架或不同的可用区。<br/>
|
|
|
-<code>repliant</code> 节点是临时工作节点。 从集群中删除它们，不影响数据库冗余<br/>
|
|
|
-建议复制节点多于核心节点。<br/>
|
|
|
+选择节点的角色。</br>
|
|
|
+<code>core</code> 节点提供数据的持久性，并负责写入。建议将核心节点放置在不同的机架或不同的可用区。</br>
|
|
|
+<code>repliant</code> 节点是临时工作节点。 从集群中删除它们，不影响数据库冗余</br>
|
|
|
+建议复制节点多于核心节点。</br>
|
|
|
注意：该参数仅在设置<code>backend</code>时生效到 <code>rlog</code>。
|
|
|
"""
|
|
|
}
|
|
|
@@ -574,17 +574,17 @@ to <code>rlog</code>.
|
|
|
db_core_nodes {
|
|
|
desc {
|
|
|
en: """
|
|
|
-List of core nodes that the replicant will connect to.<br/>
|
|
|
+List of core nodes that the replicant will connect to.</br>
|
|
|
Note: this parameter only takes effect when the <code>backend</code> is set
|
|
|
-to <code>rlog</code> and the <code>role</code> is set to <code>replicant</code>.<br/>
|
|
|
-This value needs to be defined for manual or static cluster discovery mechanisms.<br/>
|
|
|
+to <code>rlog</code> and the <code>role</code> is set to <code>replicant</code>.</br>
|
|
|
+This value needs to be defined for manual or static cluster discovery mechanisms.</br>
|
|
|
If an automatic cluster discovery mechanism is being used (such as <code>etcd</code>),
|
|
|
there is no need to set this value.
|
|
|
"""
|
|
|
- zh: """当前节点连接的核心节点列表。<br/>
|
|
|
+ zh: """当前节点连接的核心节点列表。</br>
|
|
|
注意：该参数仅在设置<code>backend</code>时生效到 <code>rlog</code>
|
|
|
-并且设置<code>role</code>为<code>replicant</code>时生效。<br/>
|
|
|
-该值需要在手动或静态集群发现机制下设置。<br/>
|
|
|
+并且设置<code>role</code>为<code>replicant</code>时生效。</br>
|
|
|
+该值需要在手动或静态集群发现机制下设置。</br>
|
|
|
如果使用了自动集群发现机制（如<code>etcd</code>），则不需要设置该值。
|
|
|
"""
|
|
|
}
|
|
|
@@ -621,15 +621,15 @@ transaction log entry.
|
|
|
|
|
|
db_default_shard_transport {
|
|
|
desc {
|
|
|
- en: """Defines the default transport for pushing transaction logs.<br/>
|
|
|
+ en: """Defines the default transport for pushing transaction logs.</br>
|
|
|
This may be overridden on a per-shard basis in <code>db.shard_transports</code>.
|
|
|
<code>gen_rpc</code> uses the <code>gen_rpc</code> library,
|
|
|
-<code>distr</code> uses the Erlang distribution.<br/>"""
|
|
|
+<code>distr</code> uses the Erlang distribution.</br>"""
|
|
|
zh: """
|
|
|
-定义用于推送事务日志的默认传输。<br/>
|
|
|
+定义用于推送事务日志的默认传输。</br>
|
|
|
这可以在 <code>db.shard_transports</code> 中基于每个分片被覆盖。
|
|
|
<code>gen_rpc</code> 使用 <code>gen_rpc</code> 库，
|
|
|
-<code>distr</code> 使用 Erlang 发行版。<br/>
|
|
|
+<code>distr</code> 使用 Erlang 发行版。</br>
|
|
|
"""
|
|
|
}
|
|
|
label {
|
|
|
@@ -640,14 +640,14 @@ This may be overridden on a per-shard basis in <code>db.shard_transports</code>.
|
|
|
|
|
|
db_shard_transports {
|
|
|
desc {
|
|
|
- en: """Allows to tune the transport method used for transaction log replication, on a per-shard basis.<br/>
|
|
|
+ en: """Allows to tune the transport method used for transaction log replication, on a per-shard basis.</br>
|
|
|
<code>gen_rpc</code> uses the <code>gen_rpc</code> library,
|
|
|
-<code>distr</code> uses the Erlang distribution.<br/>If not specified,
|
|
|
+<code>distr</code> uses the Erlang distribution.</br>If not specified,
|
|
|
the default is to use the value set in <code>db.default_shard_transport</code>."""
|
|
|
zh: """
|
|
|
-把事务日志复制到每个分片时的传输方法。<br/>
|
|
|
+把事务日志复制到每个分片时的传输方法。</br>
|
|
|
<code>gen_rpc</code> 使用 <code>gen_rpc</code> 库，
|
|
|
-<code>distr</code> 使用 Erlang 发行版。<br/>如果未指定，
|
|
|
+<code>distr</code> 使用 Erlang 发行版。</br>如果未指定，
|
|
|
默认是使用 <code>db.default_shard_transport</code> 中设置的值。
|
|
|
"""
|
|
|
}
|
|
|
@@ -728,12 +728,12 @@ Ensure that the number of completed transactions is less than the <code>max_hist
|
|
|
|
|
|
rpc_port_discovery {
|
|
|
desc {
|
|
|
- en: """<code>manual</code>: discover ports by <code>tcp_server_port</code>.<br/>
|
|
|
+ en: """<code>manual</code>: discover ports by <code>tcp_server_port</code>.</br>
|
|
|
<code>stateless</code>: discover ports in a stateless manner, using the following algorithm.
|
|
|
If node name is <code>emqxN@127.0.0.1</code>, where the N is an integer,
|
|
|
then the listening port will be 5370 + N."""
|
|
|
zh: """<code>manual</code>: 通过 <code>tcp_server_port</code> 来发现端口。
|
|
|
-<br/><code>stateless</code>: 使用无状态的方式来发现端口，使用如下算法。如果节点名称是 <code>
|
|
|
+</br><code>stateless</code>: 使用无状态的方式来发现端口，使用如下算法。如果节点名称是 <code>
|
|
|
emqxN@127.0.0.1</code>, N 是一个数字，那么监听端口就是 5370 + N。
|
|
|
"""
|
|
|
}
|
|
|
@@ -745,9 +745,9 @@ emqxN@127.0.0.1</code>, N 是一个数字，那么监听端口就是 5370 + N。
|
|
|
|
|
|
rpc_tcp_server_port {
|
|
|
desc {
|
|
|
- en: """Listening port used by RPC local service.<br/>
|
|
|
+ en: """Listening port used by RPC local service.</br>
|
|
|
Note that this config only takes effect when rpc.port_discovery is set to manual."""
|
|
|
- zh: """RPC 本地服务使用的 TCP 端口。<br/>
|
|
|
+ zh: """RPC 本地服务使用的 TCP 端口。</br>
|
|
|
只有当 rpc.port_discovery 设置为 manual 时，此配置才会生效。
|
|
|
"""
|
|
|
}
|
|
|
@@ -759,10 +759,10 @@ Note that this config only takes effect when rpc.port_discovery is set to manual
|
|
|
|
|
|
rpc_ssl_server_port {
|
|
|
desc {
|
|
|
- en: """Listening port used by RPC local service.<br/>
|
|
|
+ en: """Listening port used by RPC local service.</br>
|
|
|
Note that this config only takes effect when rpc.port_discovery is set to manual
|
|
|
and <code>driver</code> is set to <code>ssl</code>."""
|
|
|
- zh: """RPC 本地服务使用的监听SSL端口。<br/>
|
|
|
+ zh: """RPC 本地服务使用的监听SSL端口。</br>
|
|
|
只有当 rpc.port_discovery 设置为 manual 且 <code> dirver </code> 设置为 <code>ssl</code>，
|
|
|
此配置才会生效。
|
|
|
"""
|
|
|
@@ -812,9 +812,9 @@ Note that this config only takes effect when <code>rpc.driver</code> is set to <
|
|
|
|
|
|
rpc_keyfile {
|
|
|
desc {
|
|
|
- en: """Path to the private key file for the <code>rpc.certfile</code>.<br/>
|
|
|
+ en: """Path to the private key file for the <code>rpc.certfile</code>.</br>
|
|
|
Note: contents of this file are secret, so it's necessary to set permissions to 600."""
|
|
|
- zh: """<code>rpc.certfile</code> 的私钥文件的路径。<br/>
|
|
|
+ zh: """<code>rpc.certfile</code> 的私钥文件的路径。</br>
|
|
|
注意：此文件内容是私钥，所以需要设置权限为 600。
|
|
|
"""
|
|
|
}
|
|
|
@@ -826,9 +826,9 @@ Note: contents of this file are secret, so it's necessary to set permissions to
|
|
|
|
|
|
rpc_cacertfile {
|
|
|
desc {
|
|
|
- en: """Path to certification authority TLS certificate file used to validate <code>rpc.certfile</code>.<br/>
|
|
|
+ en: """Path to certification authority TLS certificate file used to validate <code>rpc.certfile</code>.</br>
|
|
|
Note: certificates of all nodes in the cluster must be signed by the same CA."""
|
|
|
- zh: """验证 <code>rpc.certfile</code> 的 CA 证书文件的路径。<br/>
|
|
|
+ zh: """验证 <code>rpc.certfile</code> 的 CA 证书文件的路径。</br>
|
|
|
注意：集群中所有节点的证书必须使用同一个 CA 签发。
|
|
|
"""
|
|
|
}
|
|
|
@@ -1039,8 +1039,8 @@ until the RPC connection is considered lost."""
|
|
|
|
|
|
console_handler_drop_mode_qlen {
|
|
|
desc {
|
|
|
- en: """When the number of buffered log events is larger than this value, the new log events are dropped.<br/>When drop mode is activated or deactivated, a message is printed in the logs."""
|
|
|
- zh: """当缓冲的日志事件数大于此值时，新的日志事件将被丢弃。<br/>启用或停用丢弃模式时，会在日志中打印一条消息。"""
|
|
|
+ en: """When the number of buffered log events is larger than this value, the new log events are dropped.</br>When drop mode is activated or deactivated, a message is printed in the logs."""
|
|
|
+ zh: """当缓冲的日志事件数大于此值时，新的日志事件将被丢弃。</br>启用或停用丢弃模式时，会在日志中打印一条消息。"""
|
|
|
}
|
|
|
label {
|
|
|
en: "Drop Mode Max Log Events"
|
|
|
@@ -1186,8 +1186,8 @@ until the RPC connection is considered lost."""
|
|
|
|
|
|
log_file_handler_drop_mode_qlen {
|
|
|
desc {
|
|
|
- en: """When the number of buffered log events is larger than this value, the new log events are dropped.<br/>When drop mode is activated or deactivated, a message is printed in the logs."""
|
|
|
- zh: """当缓冲的日志事件数大于此值时，新的日志事件将被丢弃。<br/>启用或停用丢弃模式时，会在日志中打印一条消息。"""
|
|
|
+ en: """When the number of buffered log events is larger than this value, the new log events are dropped.</br>When drop mode is activated or deactivated, a message is printed in the logs."""
|
|
|
+ zh: """当缓冲的日志事件数大于此值时，新的日志事件将被丢弃。</br>启用或停用丢弃模式时，会在日志中打印一条消息。"""
|
|
|
}
|
|
|
label {
|
|
|
en: "Drop Mode Max Log Events"
|
|
|
@@ -1334,17 +1334,17 @@ until the RPC connection is considered lost."""
|
|
|
authorization {
|
|
|
desc {
|
|
|
en: """
|
|
|
-Authorization a.k.a. ACL.<br>
|
|
|
-In EMQX, MQTT client access control is extremely flexible.<br>
|
|
|
+Authorization a.k.a. ACL.</br>
|
|
|
+In EMQX, MQTT client access control is extremely flexible.</br>
|
|
|
An out-of-the-box set of authorization data sources are supported.
|
|
|
-For example,<br>
|
|
|
-'file' source is to support concise and yet generic ACL rules in a file;<br>
|
|
|
+For example,</br>
|
|
|
+'file' source is to support concise and yet generic ACL rules in a file;</br>
|
|
|
'built_in_database' source can be used to store per-client customizable rule sets,
|
|
|
-natively in the EMQX node;<br>
|
|
|
-'http' source to make EMQX call an external HTTP API to make the decision;<br>
|
|
|
-'PostgreSQL' etc. to look up clients or rules from external databases;<br>
|
|
|
+natively in the EMQX node;</br>
|
|
|
+'http' source to make EMQX call an external HTTP API to make the decision;</br>
|
|
|
+'PostgreSQL' etc. to look up clients or rules from external databases;</br>
|
|
|
"""
|
|
|
- zh: """ 授权（ACL）。EMQX 支持完整的客户端访问控制（ACL）。<br> """
|
|
|
+ zh: """ 授权（ACL）。EMQX 支持完整的客户端访问控制（ACL）。</br> """
|
|
|
}
|
|
|
label {
|
|
|
en: "Authorization"
|
|
|
@@ -1354,9 +1354,9 @@ natively in the EMQX node;<br>
|
|
|
|
|
|
desc_cluster {
|
|
|
desc {
|
|
|
- en: """EMQX nodes can form a cluster to scale up the total capacity.<br>
|
|
|
+ en: """EMQX nodes can form a cluster to scale up the total capacity.</br>
|
|
|
Here holds the configs to instruct how individual nodes can discover each other."""
|
|
|
- zh: """EMQX 节点可以组成一个集群，以提高总容量。<br> 这里指定了节点之间如何连接。"""
|
|
|
+ zh: """EMQX 节点可以组成一个集群，以提高总容量。</br> 这里指定了节点之间如何连接。"""
|
|
|
}
|
|
|
label {
|
|
|
en: "Cluster"
|
|
|
@@ -1455,11 +1455,11 @@ The new node joins the cluster by connecting to one of the bootstrap nodes."""
|
|
|
|
|
|
desc_rpc {
|
|
|
desc {
|
|
|
- en: """EMQX uses a library called <code>gen_rpc</code> for inter-broker communication.<br/>
|
|
|
+ en: """EMQX uses a library called <code>gen_rpc</code> for inter-broker communication.</br>
|
|
|
Most of the time the default config should work,
|
|
|
but in case you need to do performance fine-tuning or experiment a bit,
|
|
|
this is where to look."""
|
|
|
- zh: """EMQX 使用 <code>gen_rpc</code> 库来实现跨节点通信。<br/>
|
|
|
+ zh: """EMQX 使用 <code>gen_rpc</code> 库来实现跨节点通信。</br>
|
|
|
大多数情况下，默认的配置应该可以工作，但如果你需要做一些性能优化或者实验，可以尝试调整这些参数。"""
|
|
|
}
|
|
|
label {
|
|
|
@@ -1504,8 +1504,15 @@ Each sink is represented by a _log handler_, which can be configured independent
|
|
|
|
|
|
desc_log_rotation {
|
|
|
desc {
|
|
|
- en: """By default, the logs are stored in `./log` directory (for installation from zip file) or in `/var/log/emqx` (for binary installation).<br/>This section of the configuration controls the number of files kept for each log handler."""
|
|
|
- zh: """默认情况下，日志存储在 `./log` 目录（用于从 zip 文件安装）或 `/var/log/emqx`（用于二进制安装）。<br/>这部分配置，控制每个日志处理进程保留的文件数量。"""
|
|
|
+ en: """
|
|
|
+By default, the logs are stored in `./log` directory (for installation from zip file) or in `/var/log/emqx` (for binary installation).</br>
|
|
|
+This section of the configuration controls the number of files kept for each log handler.
|
|
|
+"""
|
|
|
+ zh:
|
|
|
+"""
|
|
|
+默认情况下，日志存储在 `./log` 目录（用于从 zip 文件安装）或 `/var/log/emqx`（用于二进制安装）。</br>
|
|
|
+这部分配置，控制每个日志处理进程保留的文件数量。
|
|
|
+"""
|
|
|
}
|
|
|
label {
|
|
|
en: "Log Rotation"
|
|
|
@@ -1515,8 +1522,14 @@ Each sink is represented by a _log handler_, which can be configured independent
|
|
|
|
|
|
desc_log_overload_kill {
|
|
|
desc {
|
|
|
- en: """Log overload kill features an overload protection that activates when the log handlers use too much memory or have too many buffered log messages.<br/>When the overload is detected, the log handler is terminated and restarted after a cooldown period."""
|
|
|
- zh: """日志过载终止，具有过载保护功能。当日志处理进程使用过多内存，或者缓存的日志消息过多时该功能被激活。<br/>检测到过载时，日志处理进程将终止，并在冷却期后重新启动。"""
|
|
|
+ en: """
|
|
|
+Log overload kill features an overload protection that activates when the log handlers use too much memory or have too many buffered log messages.</br>
|
|
|
+When the overload is detected, the log handler is terminated and restarted after a cooldown period.
|
|
|
+"""
|
|
|
+ zh: """
|
|
|
+日志过载终止，具有过载保护功能。当日志处理进程使用过多内存，或者缓存的日志消息过多时该功能被激活。</br>
|
|
|
+检测到过载时，日志处理进程将终止，并在冷却期后重新启动。
|
|
|
+"""
|
|
|
}
|
|
|
label {
|
|
|
en: "Log Overload Kill"
|
JimMoen