I just realized a better question might be: is it safe to grep out the
following line from the replication status results?
nsds5replicaLastUpdateStatus: 1 Can't acquire busy replica
Or can that error message occur in a situation where the replica somehow stays
permanently busy, and hence failed
Thanks for that. I had looked into that but it was a bit heavyweight compared
to what we are trying to do. I was hoping there was an easy way to simply have
the command-line ignore the condition where the servers were temporarily busy.
We are using AWS and having CloudWatch store statistics an
