Comment 3 for bug 1779682

I wonder 2 things:

1) We have seen this happen where 1 controller takes a while to respond to an upgrade request, causing things to go into a 'split' upgrade. Where 2 of the machines are trying to upgrade with one doc, and the other is stuck on another doc, and since 2 think the upgrade is aborted, they never report on the new doc, and they all end up pending because they don't see all 3 controllers agree that it is time to upgrade.
2) One reason controllers weren't shutting down is that they weren't disabling new incoming requests when they were in 'shutdown' mode. And they were stuck running, because a new login would come in before the last connection was rejected. I believe we already have a patch for that in 2.4 (from Tim) that rejects incoming connections and still allows for graceful shutdown of existing connections.

I wonder if we've shrunk the 2-upgrade-doc issue such that it isn't a problem now.