-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update info docs with two buffer limit metrics. #2520
Update info docs with two buffer limit metrics. #2520
Conversation
👷 Deploy request for redis-doc pending review.Visit the deploys page to approve it
|
Got some spell check errors which are irrelevant to my changes ...
|
b1e4d79
to
6fb7c48
Compare
6fb7c48
to
266e776
Compare
commands/info.md
Outdated
@@ -300,8 +300,10 @@ Here is the meaning of all fields in the **stats** section: | |||
* `total_writes_processed`: Total number of write events processed | |||
* `io_threaded_reads_processed`: Number of read events processed by the main and I/O threads | |||
* `io_threaded_writes_processed`: Number of write events processed by the main and I/O threads | |||
* `stat_reply_buffer_shrinks`: Total number of output buffer shrinks | |||
* `stat_reply_buffer_expands`: Total number of output buffer expands | |||
* `client_query_buffer_limit_disconnections`: Total number of clients reached query buffer length limit |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how about "Total number of disconnections due to the client reached query buffer limit" and "Total number of disconnections due to the client reached output buffer limit"
I would like to emphasize the "disconnection".
In redis/redis#12476 two new info merics are added:
client_query_buffer_limit_reached
andclient_output_buffer_limit_reached
.Also correct the info of
reply_buffer_shrinks
andreply_buffer_expands
.