Cannot fix search count as the bucket hasn't rolled yet.
AND
Missing enough suitable candidates to create searchable copy in order to meet replication policy. Missing={ default:1 }
AND
cannot fix up search factor as bucket is not serviceable
There could be a few issues:
1) network delay between indexers/CMs to replicate the bucket across nodes.
2) the Cluster master taking time to update the status and show that in dashboard.
3) Restart the cluster master and allow time for it to catch up ... eventually the bucket status messages should be gone.