[
https://issues.apache.org/jira/browse/HDDS-8043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sammi Chen updated HDDS-8043:
-----------------------------
Description:
Previously rocksdb statistics are not enabled by default due to
# there are two many rocksdb instances on DN. It's hard to find the
information of one specific container rocksdb instance. So for DN, this
function is actually not usable.
# enable rocksdb statistics may have performance impact on rocksdb operation,
around 5%~10%. [Link.|https://github.com/facebook/rocksdb/wiki/Statistics]
Now with schema V3, one rocksdb per volume, there is only a few number of
rocksdb instances. Although the rocksdb statistics may introduce some
performance overhead of rocksdb operation, but the overall rocksdb opeation
execution time is only one part of service execution time, and it is very
useful for real-time rocksdb related diagnose and investigation if statistics
are on. Otherwise, it requires configuration change, restart service, waiting
until the issue reproduced.
was:
Previously rocksdb statistics are not enabled by default due to
# there are two many rocksdb instances on DN. It's hard to find the
information of one specific container rocksdb instance. So for DN, this
function is actually not usable.
# enable rocksdb statistics may have performance impact, around 5%~10%.
[Link.|https://github.com/facebook/rocksdb/wiki/Statistics]
Now with schema V3, one rocksdb per volume, there is only a few number of
rocksdb instances. Although the rocksdb statistics may introduce some
performance overhead, but it's very useful for real-time rocksdb performance
diagnose and investigation.
> Enable rocksdb statistics metrics by default
> --------------------------------------------
>
> Key: HDDS-8043
> URL: https://issues.apache.org/jira/browse/HDDS-8043
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: Sammi Chen
> Assignee: Sammi Chen
> Priority: Major
>
> Previously rocksdb statistics are not enabled by default due to
> # there are two many rocksdb instances on DN. It's hard to find the
> information of one specific container rocksdb instance. So for DN, this
> function is actually not usable.
> # enable rocksdb statistics may have performance impact on rocksdb
> operation, around 5%~10%.
> [Link.|https://github.com/facebook/rocksdb/wiki/Statistics]
> Now with schema V3, one rocksdb per volume, there is only a few number of
> rocksdb instances. Although the rocksdb statistics may introduce some
> performance overhead of rocksdb operation, but the overall rocksdb opeation
> execution time is only one part of service execution time, and it is very
> useful for real-time rocksdb related diagnose and investigation if statistics
> are on. Otherwise, it requires configuration change, restart service,
> waiting until the issue reproduced.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
