Was this page helpful?
Caution
You're viewing documentation for an unstable version of ScyllaDB Enterprise. Switch to the latest stable version.
Failed Decommission¶
This article describes the troubleshooting procedure when node decommission fails.
During decommissioning, the streaming process starts, and the node streams its data to the other nodes in the ScyllaDB cluster. The process may fail if the node fails to read from the HDD or a network problem occurs.
Problem¶
The node is stuck in the decommission status.
How to Verify¶
Run the nodetool status command to check the node status. The expected result is UL (Up Leaving).
Check the node status from the other nodes in the cluster to verify that the status of the decommissioned node status is UL.
Note
The nodetool netstats command does not show ongoing streaming.
The following error message will appear in the logs:
nodetool: ScyllaDB API server HTTP POST to URL '/storage_service/decommission' failed: stream_ranges failed
Solution¶
Restart the node you are decommissioning.
sudo systemctl restart scylla-server
docker exec -it some-scylla supervisorctl restart scylla
(without restarting some-scylla container)
Run the
nodetool statuscommand to verify the node is inUNstatus.Run
nodetool decommissionagain.