|
@@ -894,7 +894,7 @@ conn_congestion {
|
|
|
## Whether to alarm the congested connections.
|
|
## Whether to alarm the congested connections.
|
|
|
##
|
|
##
|
|
|
## Sometimes the mqtt connection (usually an MQTT subscriber) may
|
|
## Sometimes the mqtt connection (usually an MQTT subscriber) may
|
|
|
- ## get "congested", because there're too many packets to be sent.
|
|
|
|
|
|
|
+ ## get "congested", because there's too many packets to sent.
|
|
|
## The socket tries to buffer the packets until the buffer is
|
|
## The socket tries to buffer the packets until the buffer is
|
|
|
## full. If more packets come after that, the packets will be
|
|
## full. If more packets come after that, the packets will be
|
|
|
## "pending" in a queue and we consider the connection is
|
|
## "pending" in a queue and we consider the connection is
|
|
@@ -914,7 +914,7 @@ conn_congestion {
|
|
|
enable_alarm = true
|
|
enable_alarm = true
|
|
|
|
|
|
|
|
## Won't clear the congested alarm in how long time.
|
|
## Won't clear the congested alarm in how long time.
|
|
|
- ## The alarm is cleared only when there're no pending bytes in
|
|
|
|
|
|
|
+ ## The alarm is cleared only when there's no pending bytes in
|
|
|
## the queue, and also it has been `min_alarm_sustain_duration`
|
|
## the queue, and also it has been `min_alarm_sustain_duration`
|
|
|
## time since the last time we considered the connection is "congested".
|
|
## time since the last time we considered the connection is "congested".
|
|
|
##
|
|
##
|