[IGNITE-14575] Write to Distributed Metastorage should throw exception on client if client is not connected to topology

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.10
• Fix Version/s: 2.11
• Release Note: Write to Distributed Metastorage now throws exception on client if client is not connected to topology
• Ignite Flags: Release Notes Required
• Assignee: Semyon Danilov
• Reporter: Semyon Danilov
• Created: 16/Apr/21 13:15
• Updated: 25/Nov/21 13:28
• Resolved: 04/May/21 07:39

Description

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.

Issue Links

• links to: GitHub Pull Request #9012
• links to: GitHub Pull Request #9100