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

Semyon Zikunov updated IGNITE-23138:
------------------------------------
    Attachment: runKeyCollisionsMetric_analysis_en.txt

> Fix TxWithKeyContentionSelfTest (Cache 12 group)
> ------------------------------------------------
>
>                 Key: IGNITE-23138
>                 URL: https://issues.apache.org/jira/browse/IGNITE-23138
>             Project: Ignite
>          Issue Type: Test
>            Reporter: Semyon Zikunov
>            Assignee: Semyon Zikunov
>            Priority: Trivial
>              Labels: ise
>         Attachments: runKeyCollisionsMetric_analysis_en.txt, 
> runKeyCollisionsMetric_analysis_ru.txt
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> *Description:* The following tests are intermittently failing due to an 
> {{AssertionError}} in Apache Ignite:
>  * {{testOptimisticReadCommittedCheckContentionTxMetricNear}}
>  * {{testOptimisticRepeatableReadCheckContentionTxMetric}}
>  * {{testOptimisticReadCommittedCheckContentionTxMetric}}
>  * {{testOptimisticRepeatableReadCheckContentionTxMetricNear}}
>  * {{testPessimisticRepeatableReadCheckContentionTxMetric}}
>  * {{testPessimisticRepeatableReadCheckContentionTxMetricNear}}
> The issue arises when the tests periodically fail at the 
> {{assertTrue(GridTestUtils.waitForCondition())}} check. The condition 
> compares the {{txKeyCollisions}} field in the transaction metrics, which 
> sometimes returns an empty string. This leads to an {{AssertionError}} when 
> attempting to validate {{{}coll1{}}}, indicating possible inconsistencies or 
> timing issues with the metrics collection during test execution.
> *Tasks:*
>  # Investigate the root cause of the {{txKeyCollisions}} field occasionally 
> returning an empty string in the metrics.
>  # Analyze whether timing or state propagation issues are causing the 
> {{waitForCondition}} to pass before the {{txKeyCollisions}} metrics are 
> populated.
>  # Refactor the tests to ensure consistent metrics collection and validation, 
> possibly adding additional synchronization or checks.
>  # Verify the fix by running the tests repeatedly to confirm the flaky 
> behavior is resolved.
> *Expected Result:* The tests run reliably without intermittent failures. The 
> {{txKeyCollisions}} metrics are consistently populated, and the 
> {{assertTrue}} check passes as expected, ensuring the tests no longer exhibit 
> flakiness.



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

Reply via email to