[
https://issues.apache.org/jira/browse/IGNITE-14575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17346223#comment-17346223
]
Sergey Chugunov commented on IGNITE-14575:
------------------------------------------
[~mmuzaf],
Lets take a short timeout (say, one extra day) and give the proper fix a
chance. It is already in progress and now waiting just for green visa.
If everything goes smoothly we'll get the issue fixed and preserve clean master
history without revert commits.
If the fix isn't merged till the end of tomorrow, I'm OK with reverting current
patch and integrating it with the fix.
Does it make sense to you?
> 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: 50m
> 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)
