You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vyacheslav Koptilin (Jira)" <ji...@apache.org> on 2022/11/01 12:20:00 UTC
[jira] [Updated] (IGNITE-17967) RO writeIntent resolution tests hang up in case of multi node cluster
[ https://issues.apache.org/jira/browse/IGNITE-17967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vyacheslav Koptilin updated IGNITE-17967:
-----------------------------------------
Labels: ignite-3 transaction3_ro (was: transaction3_ro)
> RO writeIntent resolution tests hang up in case of multi node cluster
> ---------------------------------------------------------------------
>
> Key: IGNITE-17967
> URL: https://issues.apache.org/jira/browse/IGNITE-17967
> Project: Ignite
> Issue Type: Bug
> Reporter: Alexander Lapin
> Assignee: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-3, transaction3_ro
> Fix For: 3.0.0-beta1
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {code:java}
> TxAbstractTest#testReadOnlyGetWriteIntentResolutionUpdate{code}
> works in case of single node cluster but hangs up in case of multi node one.
> It also worth to mention that simple get tests without writeIntent resolution e.g.
> {code:java}
> TxAbstractTest#testReadOnlyGet{code}
> works both on sinle and multi node cluster.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)