[
https://issues.apache.org/jira/browse/HDDS-5033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-5033:
----------------------------
Description:
After restart DN, the SCM may not know the full ports of that DN
Please check attachment.
After restart SCM, this issue gone.
The issue should be: SCMNodeManager just record the DatanodeDetails once during
register.
But for DN, it won’t record the admin, server, client port into DatanodeDetails
until its ratis server is up.
Thus there is contention here: if the register request is reported before ratis
server is up, SCM won’t know full port list of that DN.
> SCM may not be able to learn full port list of Datanode after Datanode is
> restarted.
> ------------------------------------------------------------------------------------
>
> Key: HDDS-5033
> URL: https://issues.apache.org/jira/browse/HDDS-5033
> Project: Apache Ozone
> Issue Type: Bug
> Components: SCM
> Affects Versions: 1.2.0
> Reporter: Glen Geng
> Priority: Major
> Attachments: 企业微信截图_097abd79-0ea4-487b-9b07-6bc2330385ef.png,
> 企业微信截图_c0bd5dde-98ee-4350-914d-2e0069ea8602.png
>
>
> After restart DN, the SCM may not know the full ports of that DN
> Please check attachment.
>
> After restart SCM, this issue gone.
> The issue should be: SCMNodeManager just record the DatanodeDetails once
> during register.
> But for DN, it won’t record the admin, server, client port into
> DatanodeDetails until its ratis server is up.
> Thus there is contention here: if the register request is reported before
> ratis server is up, SCM won’t know full port list of that DN.
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
