[
https://issues.apache.org/jira/browse/HDDS-11331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17874433#comment-17874433
]
JiangHua Zhu edited comment on HDDS-11331 at 8/17/24 5:42 AM:
--------------------------------------------------------------
[~szetszwo], I think a new interface should be added to
StorageContainerDatanodeProtocol for Datanode to report node information to SCM
regularly.
This interface is a supplement to solve this problem.
{code:java}
public interface StorageContainerDatanodeProtocol {
......
SCMHeartbeatResponseProto sendLifeline(NodeReportProto nodeReport)
throws IOException;
......
}
{code}
What do you think? [~szetszwo]
was (Author: jianghuazhu):
[~szetszwo], I think a new interface should be added to
StorageContainerDatanodeProtocol for Datanode to report node information to SCM
regularly.
{code:java}
public interface StorageContainerDatanodeProtocol {
......
SCMHeartbeatResponseProto sendLifeline(NodeReportProto nodeReport)
throws IOException;
......
}
{code}
What do you think? [~szetszwo]
> Datanode cannot report for a long time
> --------------------------------------
>
> Key: HDDS-11331
> URL: https://issues.apache.org/jira/browse/HDDS-11331
> Project: Apache Ozone
> Issue Type: Improvement
> Components: DN
> Affects Versions: 1.4.0
> Reporter: JiangHua Zhu
> Assignee: JiangHua Zhu
> Priority: Major
> Attachments: 1505js.1, screenshot-1.png, screenshot-2.png,
> screenshot-3.png, screenshot-4.png, screenshot-5.png
>
>
> SCM shows that some Datanodes cannot report for a long time, and their status
> is DEAD or STALE.
> I printed jstack information, which shows that StateContext#pipelineActions
> is stuck and cannot report to SCM/Recon.
> The jstack information has been uploaded as an attachment.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
