Cause of problem:

1. The reason for this problem is that the original slice was not properly closed and cleaned up, so there is no way to get a slice lock when the slice has to be reallocated back to the problem node.
2. This does not cause the slice data to be lost, it just needs to retrigger the allocation

Recovery instruction

curl -XPOST http://localhost:9200/_cluster/reroute?retry_failed

View details

curl -XGET http://localhost:9200/_cluster/allocation/explain

Read More:

• [Solved] k8s kubeadmin init Error: http://localhost:10248/healthz‘ failed
• Solve Error: call_and_retry_last allocation failed – javascript heap out of memory
• Git: “error: RPC failed; curl 18 transfer closed with outstanding read data remaining”
• Node Kubelet Error: node “xxxxx“ not found [How to Solve]
• Go Slice Error: panic:runtime error:index out of range [0] with length 0 [Solved]
• openlayers — Cannot read property ‘slice‘ of null—Map cannot be loaded
• [Solved] K8s Initialize Error: failed with error: Get “http://localhost:10248/healthz“
• How to Solve Go Error: concurrent map iteration and map write
• [Solved] Error running query: MetaException(message:Got exception: java.net.ConnectException Call From XXXX
• How to Solve Rabbitmq Error: Failed to start RabbitMQ broker
• An error occurred: Sorry,Faithfully yours, nginx Error
• org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘globalTransa
• [Solved] Android Studio Run Error: Error while executing: am start -n
• Golang Error: fatal error: concurrent map read and map writ
• ERROR: dependencies ‘curl’, ‘openssl’ are not available for package ‘httr’
• RPC failed; curl 56 SSLRead() return error
• How to Solve “Error db.num is null” when starting Nacos
• OpenSSL: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failur
• [Solved] Kubeadm Reset error: etcdserver: re-configuration failed due to not enough started members