You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Dmitry Pavlov (Jira)" <ji...@apache.org> on 2026/07/15 07:10:00 UTC

[jira] [Assigned] (IGNITE-28795) [doc] Document SizeUsedByData metric for data region monitoring

     [ https://issues.apache.org/jira/browse/IGNITE-28795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmitry Pavlov reassigned IGNITE-28795:
--------------------------------------

    Assignee: Ignite TC Bot

> [doc] Document SizeUsedByData metric for data region monitoring
> ---------------------------------------------------------------
>
>                 Key: IGNITE-28795
>                 URL: https://issues.apache.org/jira/browse/IGNITE-28795
>             Project: Ignite
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Ignite TC Bot
>            Assignee: Ignite TC Bot
>            Priority: Major
>              Labels: docs-ux, ise
>             Fix For: 2.18, 2.19
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> The SizeUsedByData metric is available in the io.dataregion.{region_name} registry, but it is not described in the user documentation.
> Current docs explain data region monitoring through TotalAllocatedSize, PagesFillFactor, TotalUsedPages, PhysicalMemoryPages, and PhysicalMemorySize, and the control.sh metric example for io.dataregion.default does not include SizeUsedByData.
> This follow-up should document:
> - what SizeUsedByData represents
> - how it differs from TotalAllocatedSize, OffheapUsedSize, and PhysicalMemorySize
> - how to use it when monitoring data region usage
> - the updated io.dataregion metric listing and control.sh example output
> Related implementation origin: IGNITE-17728 Improve data size-related metrics.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)