Wei-Chiu Chuang created HDDS-15955:
--------------------------------------
Summary: [Docs] Troubleshooting Ozone connectivity problem in
Kubernetes environment
Key: HDDS-15955
URL: https://issues.apache.org/jira/browse/HDDS-15955
Project: Apache Ozone
Issue Type: Sub-task
Components: documentation
Reporter: Wei-Chiu Chuang
[https://ozone.apache.org/docs/next/troubleshooting/client-connectivity]
mentioned hdds.datanode.use.datanode.hostname configuration change is required
for Kuberntes.
There are two other configuration changes required for Kuberntes. We should add
these two to the same doc or add to the Kubernetes doc
[https://ozone.apache.org/docs/next/quick-start/installation/kubernetes/] or
make a dedicated troubleshooting doc for Kubernetes deployments.
{noformat}
<property>
<name>ozone.network.flexible.fqdn.resolution.enabled</name>
<tag>OZONE, SCM, OM</tag>
<value>false</value>
<description>SCM, OM hosts will be able to resolve itself based on its host
name instead of fqdn. It is useful for deploying to kubernetes
environment, during the initial launching time when
[pod_name].[service_name] is not resolvable yet because of the probe.
</description>
</property>
<property>
<name>ozone.network.jvm.address.cache.enabled</name>
<tag>OZONE, SCM, OM, DATANODE</tag>
<value>true</value>
<description>Disable the jvm network address cache. In environment such as
kubernetes, IPs of instances of scm, om and datanodes can be changed.
Disabling this cache helps to quickly resolve the fqdn's to the new IPs.
</description>
</property> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
