-
Notifications
You must be signed in to change notification settings - Fork 473
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
Add write stall stats to info command output #396
Conversation
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.
LGTM, so speedy.
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.
should we also show "io_stalls.total_slowdown" and "io_stalls.total_stop"
Co-authored-by: Wang Yuan <wangyuancode@163.com>
@ShooterIT I don't think it's necessary to add If we all add it, we'll have too much information. |
fine, both are ok to me |
Co-authored-by: Wang Yuan <wangyuancode@163.com>
Co-authored-by: Wang Yuan <wangyuancode@163.com>
Kvrocks uses RocksDB as the storage engine. When RocksDB can't flush and compact data promptly, it uses a feature called " Write Stalls" to try and slow the amount of data coming into the engine.
This is information user should know. Currently, Kvrocks uses RocksDB's EventListener mechanism to capture stall information. The user must grep the log to get this information.
So I add it to the output of the
INFO
command so that users can get information from theINFO
command directly. It can also be easily applied to their monitor systems.