[
https://issues.apache.org/jira/browse/IGNITE-27773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-27773:
-----------------------------------------
Description:
It seems possible that the `MarkedForVacuumTransactionMetaCount` metric can be
incremented more than once for the same transaction identifier.
The vacuum process is asynchronous, which attempts to clean up tx states once
during the `RESOURCE_VACUUM_INTERVAL_MILLISECONDS` interval (30 seconds by
default). So, it is possible that we can start another attempt before the
previous one is finished, and so the corresponding tx state has not cleaned up
yet. It means that we will try to clean up the same tx and increment the
`MarkedForVacuumTransactionMetaCount` twice.
was:It seems that it is possible thatÂ
> Vacuum metrics are not accurate
> -------------------------------
>
> Key: IGNITE-27773
> URL: https://issues.apache.org/jira/browse/IGNITE-27773
> Project: Ignite
> Issue Type: Bug
> Components: metrics ai3, transactions ai3
> Affects Versions: 3.1
> Reporter: Vyacheslav Koptilin
> Priority: Major
> Labels: ignite-3
>
> It seems possible that the `MarkedForVacuumTransactionMetaCount` metric can
> be incremented more than once for the same transaction identifier.
> The vacuum process is asynchronous, which attempts to clean up tx states once
> during the `RESOURCE_VACUUM_INTERVAL_MILLISECONDS` interval (30 seconds by
> default). So, it is possible that we can start another attempt before the
> previous one is finished, and so the corresponding tx state has not cleaned
> up yet. It means that we will try to clean up the same tx and increment the
> `MarkedForVacuumTransactionMetaCount` twice.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
