Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Incomplete
-
None
-
None
-
None
Description
I often find that I choose a value for the size of the native map out of the air without really having a good understanding of why I chose it (aside from considerations of table.compaction.minor.logs.threshold and tserver.walog.max.size).
We don't have any insight into some basic metrics on the native maps. It would be nice to be able to answer questions like
- What is the utilization (space) of the native maps for a server
- How much time is the server spending writing data as opposed to allocating new blocks
I'm sure there are some other questions too.