[
https://issues.apache.org/jira/browse/IGNITE-22882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-22882:
---------------------------------------
Labels: iep-128 ignite-3 (was: ignite-3)
> Support many cluster IDs on thin client connection
> --------------------------------------------------
>
> Key: IGNITE-22882
> URL: https://issues.apache.org/jira/browse/IGNITE-22882
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
> Affects Versions: 3.0.0-beta1
> Reporter: Roman Puchkovskiy
> Assignee: Pavel Tupitsyn
> Priority: Major
> Labels: iep-128, ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> When a thin client connects, it obtains cluster ID from the server node and
> validates that this cluster ID matches previous cluster ID the client saw (if
> any).
> It should obtain N cluster IDs and check that previous cluster ID it saw (if
> any) is one of these cluster IDs.
> As the server currently can only have 1 cluster ID, it should send a list of
> just 1 cluster ID.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
