You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Ivan Bessonov (Jira)" <ji...@apache.org> on 2021/05/18 12:27:00 UTC

[jira] [Updated] (IGNITE-14729) Fix JDBC test suite flakiness after IGNITE-14575

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

Ivan Bessonov updated IGNITE-14729:
-----------------------------------
    Fix Version/s: 2.11

> Fix JDBC test suite flakiness after IGNITE-14575 
> -------------------------------------------------
>
>                 Key: IGNITE-14729
>                 URL: https://issues.apache.org/jira/browse/IGNITE-14729
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Semyon Danilov
>            Assignee: Semyon Danilov
>            Priority: Major
>             Fix For: 2.11
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> JDBC test suite went flaky after IGNITE-14575. On the first look it seems like there is a race condition: ClientImpl notifies listeners (notably, DistributedMetaStorage) about `EVT_NODE_JOINED` before `state` is set to `CONNECTED`. This way, distributed meta storage tries to perform write operations and ClientImpl is not ready yet. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)