[
https://issues.apache.org/jira/browse/IOTDB-3570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jialin Qiao reassigned IOTDB-3570:
----------------------------------
Assignee: Song Ziyang
> Extend the Peer structure of the consensus layer to embed the ID of the upper
> layer
> -----------------------------------------------------------------------------------
>
> Key: IOTDB-3570
> URL: https://issues.apache.org/jira/browse/IOTDB-3570
> Project: Apache IoTDB
> Issue Type: Improvement
> Reporter: Xinyu Tan
> Assignee: Song Ziyang
> Priority: Major
>
> Currently, the Peer returned by the getLeader interface only contains the IP
> address and port corresponding to the consensus layer of the Leader node.
> However, the port that the upper layer wants to obtain may be the service
> port that the upper layer RPC can connect to, such as internalService, etc.
> Therefore, we can consider extending the structure of the Peer so that it can
> be packed with a business custom ID structure, so that the upper layer can be
> returned at getLeader with the ID with business semantics defined for each
> Peer at AddConsensusGroup, thus reducing the coding burden on the upper
> layer. For example, DataNode can encode the TEndpoint of internalService into
> the ID
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
