nsq管理界面有很多的字段,都是什么含义呢?
字段名 | 含义 |
---|---|
Depth | Current sum of messages in memory on disk (i.e. the “backlog” of messages pending delivery) 当前消息数:内存和硬盘转存的消息数,即当前的积压量 |
Memory + Disk | 内存和硬盘分别积压的消息数 |
In-Flight | Current count of messages delivered but not yet finished (FIN), requeued (REQ) or timed out 当前未完成的消息数:包括发送但未返回FIN/重新入队列REQ/超时TIMEOUT 三种消息数之和,代表已经投递还未消费掉的消息 |
Deferred | Current count of messages that were requeued and explicitly deferred which are not yet available for delivery. 重新入队的延迟消息数,指还未发布的重入队消息数量,即未消费的定时(延时)消息数 |
Requeued | Total count of messages that have been added back to the queue due to time outs or explicit requeues.重新入队列的消息数 |
Timed Out | Total count of messages that were requeued after not receiving a response from the client before the configured timeout. 已重入队列但按配置的超时时间内还收到响应的消息数 |
Messages | Total count of new messages recieved since node startup. 节点启动后的所有新消息总数,真正的消息次数 |
Connections | Current number of connected clients. 客户端连接数 |
Client Host | Client ID (hostname) and on-hover the connection remote-address.客户端的主机名及端口 |
Protocol | NSQ protocol version and client user-agent. NSQ协议版本和客户端nsq版本信息 |
Attributes | TLS and AUTH connection state. 传输层安全和认证连接的状态 |
NSQd Host | Address of the nsqd node connected to nsqd. 节点的地址 |
In-flight | Number of messages sent on a connection which are not yet Finished or Requeued. 当前未完成的消息数:包括发送但未返回FIN/重新入队列REQ/超时TIMEOUT 三种消息数之和. |
Ready Count | Max number of messages that can be in-flight on this connection. This is controlled by a client’s max_in_flight setting. 本次连接的最大能未完成的消息数,可由客户端的 max_in_flight 参数控制,ready count比较重要,go的客户端是通过设置max-in-flight 除以客户端连接数得到的,代表一次推给客户端多少条消息,或者客户端准备一次性接受多少条消息,谨慎设置其值,因为可能造成服务器压力,如果消费能力比较弱,rdy建议设置的低一点 |
Finished | Sum of Finish (FIN) responses. 完成的消息数,即返回FIN的消息数 |
Requeued | Sum of Requeue (REQ) responses. 重新入队的消息数,即返回REQ的消息数量 |
Messages | Count of messages sent to this connection. 发送到本客户端的总消息数 |
此外,对于按钮:
Empty Queue
可以清空当前channel的信息,Delete Channel
删除当前channel, Pause Channel
是暂停消息消费(点击后为“UnPause Topic
”,为取消暂停消费,恢复消费)