[
https://issues.apache.org/jira/browse/IGNITE-14729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17346803#comment-17346803
]
Ignite TC Bot commented on IGNITE-14729:
----------------------------------------
{panel:title=Branch: [pull/9102/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9102/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6010814&buildTypeId=IgniteTests24Java8_RunAll]
> 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
> 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)
