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

Alexey Gidaspov updated IGNITE-14575:
-------------------------------------
    Release Note: Write to Distributed Metastorage now throws exception on 
client if client is not connected to topology

> 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: 1h
>  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)

Reply via email to