Troubleshooting Ozone Integration With Other Components
This section contains guides to help troubleshoot Ozone integration with other systems.
Safemode
Use this page when the Storage Container Manager (SCM) stays in safemode longer than expected after startup or a restart, and client writes fail.
Integrations
This section contains guides to help troubleshoot Ozone integration with other systems.
Security
This section contains guides to help troubleshoot security related issues in an Ozone deployment.
Decommissioning and Maintenance
A Datanode moves from DECOMMISSIONING to DECOMMISSIONED only after every container it holds is sufficiently replicated on other nodes.
OM HA snapshot installation
When a new Ozone Manager (OM) is added to an existing OM HA cluster, it needs to obtain the latest OM DB snapshot from the leader OM.
Netty native (direct) memory
Symptom
Client connectivity
Use this page when Ozone clients cannot connect to Datanodes for data transfer, even though metadata operations through the Ozone Manager still work.
Connectivity
Connection failures can cause Ozone clients and services to retry for a long time before an operation fails. Identify which connection is failing before changing retry or timeout settings.
Datanode space
Insufficient storage space can cause writes to slow down or fail. When too few Datanodes have enough space for the required replication, SCM cannot allocate new containers or pipelines and clients may retry their writes.