[
https://issues.apache.org/jira/browse/IGNITE-16526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17611354#comment-17611354
]
Aleksandr commented on IGNITE-16526:
------------------------------------
Hi [~apolovtcev], I think this ticket is a duplicate of IGNITE-17092. The
topology command is already implemented. If you don't mind, could you please
close this ticket?
> Create a CLI command for getting logical topology
> -------------------------------------------------
>
> Key: IGNITE-16526
> URL: https://issues.apache.org/jira/browse/IGNITE-16526
> Project: Ignite
> Issue Type: New Feature
> Reporter: Aleksandr Polovtcev
> Priority: Major
> Labels: ignite-3
>
> According to the join protocol, we are going to have two types of node
> topologies: "physical" (a.k.a. network) topology and "logical" topology. It
> may be convenient for the user to know which nodes have passed validation and
> have joined the logical topology, therefore it is suggested to implement a
> CLI command for this purpose.
> h2. Proposed API
> {code:java}
> ./ignite cluster topology --node-endpoint=??? {code}
> * --node-endpoint - address of the REST endpoint of the receiving node in
> host:port format
> It should return a response like the following (it can also be pretty-printed
> as a table):
> {code:java}
> consistent ID, ID, address, status
> node 1, e2d4988a-b836-4e7e-a888-2639e6f79ef0, 127.0.0.1, RUNNING
> node 2, 5cb561fc-1963-4f95-98f8-deb407669a86, 127.0.0.2, RECOVERY {code}
> * consistent ID - node consistent ID (that doesn't change between restarts)
> * ID - node local ID (that changes between restarts)
> * address - node IP address
> * status - node status. Node statuses are going to be finalized when node
> recovery is implemented and may be omitted during this feature development.
> h2. Server part
> The receiving node should read the CMG state, where the logical topology is
> persisted, or return an error in the following cases:
> * Cluster has not been initialized
> * Node has not joined any clusters
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
