[
https://issues.apache.org/jira/browse/IGNITE-17003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-17003:
----------------------------------
Ignite Flags: (was: Docs Required,Release Notes Required)
> SqlDataTypesCoverageTests.testDecimalDataType failes flaky
> ----------------------------------------------------------
>
> Key: IGNITE-17003
> URL: https://issues.apache.org/jira/browse/IGNITE-17003
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Reporter: Taras Ledkov
> Assignee: Taras Ledkov
> Priority: Major
> Fix For: 2.14
>
>
> There is a problem with this critical test - when start full test class there
> is high posibuility to get error on first tests. By default first test is
> testDecimalDataType. Every time I get different errors - it makes a
> suggestion about side effect of started cluster. Test doesn’t fail starting
> separately.
> Case of fail: [atomicityMode=ATOMIC, cacheMode=PARTITIONED, ttlFactory=null,
> backups=2, evictionFactory=null, onheapCacheEnabled=false,
> writeSyncMode=FULL_ASYNC, persistenceEnabled=false]
> *Root cause:*
> The test is invalid for {{FULL_ASYNC }}mode.
> The sequential execute
> UPDATE …
> SELECT …
> cannot guarantee visibility UPDATE changes for the SELECT query when
> FULL_ASYNC mode is used.
> *Possible fixes:*
> There can be two ways:
> don’t use FULL_ASYNC mode at the test.
> wait for UPDATE changes is applied.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
