[
https://issues.apache.org/jira/browse/IGNITE-14575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17344632#comment-17344632
]
Maxim Muzafarov commented on IGNITE-14575:
------------------------------------------
Folks, [~sdanilov], [~sergeychugunov]
Can you re-check the patch. After these changes, the JDBC Test suit starts
failing with error code 130.
In your local branch:
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_JdbcDriver?branch=pull%2F9012%2Fhead&buildTypeTab=overview&mode=builds
In the master branch in 90% of the cases:
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_JdbcDriver?branch=%3Cdefault%3E&mode=builds
> Write to Distributed Metastorage should throw exception on client if client
> is not connected to topology
> --------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-14575
> URL: https://issues.apache.org/jira/browse/IGNITE-14575
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.10
> Reporter: Semyon Danilov
> Assignee: Semyon Danilov
> Priority: Major
> Fix For: 2.11
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Reference to Distributed Metastorage can be obtained on client that hasn't
> connected to any server node yet.
> The reference allows to send write request that will be completed after
> client connect when Tcp Discovery is used and dropped on ZK Discovery.
> To make API more reliable we need to change this behavior: when client is not
> connected to any server (because there are no servers in topology yet or
> because it has disconnected from topology) all incoming write or cas requests
> should be dropped, appropriate exception should be thrown.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
