HDDS-15917. Add client connectivity troubleshooting runbook.#498
Merged
Conversation
Publish the troubleshooting section and document hdds.datanode.use.datanode.hostname for Kubernetes, remote clients, and multi-homed deployments. Co-authored-by: Cursor <cursoragent@cursor.com>
jasonosullivan34
approved these changes
Jul 21, 2026
Contributor
|
Thanks for adding this. I don't think we should be retroactively updating the versioned docs though. IMO can just add this to |
Remove mirrored troubleshooting page and versioned Kubernetes cross-links; the runbook remains in the main docs tree only. Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
Author
Let's make it an explicit rule in AGENTS.md |
Contributor
Author
|
Merged. Thanks @jasonosullivan34 @errose28 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This change adds a short troubleshooting runbook for when Ozone clients cannot reach Datanodes for data transfer, while metadata operations through the Ozone Manager still succeed. It documents setting
hdds.datanode.use.datanode.hostname=trueon clients and Datanodes for Kubernetes, port-forwarded or remote clients, and multi-homed networks, and explains why hostname mode avoids connecting to stale or unroutable IPs registered in SCM.The pull request also publishes the Troubleshooting documentation section by removing the Docusaurus docs exclude for
06-troubleshooting, and adds cross-links from the Kubernetes quick-start guide and the configuration appendix.What is the link to the Apache Jira?
https://issues.apache.org/jira/browse/HDDS-15917
How was this patch tested?
pnpm run lint(eslint, markdownlint, yamllint)npm run buildMade with Cursor