|
@@ -1024,8 +1024,8 @@ all log events are handled asynchronously. This means that the client process se
|
|
|
by calling a log function in the Logger API, does not wait for a response from the handler
|
|
by calling a log function in the Logger API, does not wait for a response from the handler
|
|
|
but continues executing immediately after the event is sent.
|
|
but continues executing immediately after the event is sent.
|
|
|
It is not affected by the time it takes the handler to print the event to the log device.
|
|
It is not affected by the time it takes the handler to print the event to the log device.
|
|
|
-If the message queue grows larger than this value, t
|
|
|
|
|
-he handler starts handling log events synchronously instead,
|
|
|
|
|
|
|
+If the message queue grows larger than this value,
|
|
|
|
|
+the handler starts handling log events synchronously instead,
|
|
|
meaning that the client process sending the event must wait for a response.
|
|
meaning that the client process sending the event must wait for a response.
|
|
|
When the handler reduces the message queue to a level below the sync_mode_qlen threshold,
|
|
When the handler reduces the message queue to a level below the sync_mode_qlen threshold,
|
|
|
asynchronous operation is resumed.
|
|
asynchronous operation is resumed.
|
|
@@ -1158,11 +1158,11 @@ When drop mode is activated or deactivated, a message is printed in the logs."""
|
|
|
log_overload_kill_enable {
|
|
log_overload_kill_enable {
|
|
|
desc {
|
|
desc {
|
|
|
en: """Enable log handler overload kill feature."""
|
|
en: """Enable log handler overload kill feature."""
|
|
|
- zh: """启用日志处理进程过载终止功能。"""
|
|
|
|
|
|
|
+ zh: """日志处理进程过载时为保护自己节点其它的业务能正常,强制杀死日志处理进程。"""
|
|
|
}
|
|
}
|
|
|
label {
|
|
label {
|
|
|
en: "Log Handler Overload Kill"
|
|
en: "Log Handler Overload Kill"
|
|
|
- zh: "日志处理进程过载终止"
|
|
|
|
|
|
|
+ zh: "日志处理进程过载保护"
|
|
|
}
|
|
}
|
|
|
}
|
|
}
|
|
|
|
|
|