Resolved - The cluster service restart earlier appears to have addressed the intermittent availability issues observed. We have updated the secondary nodes in the high availability clusters, but we're going to hold off on updating the primary nodes for three reasons. First, the service restart appears to have addressed the immediate issues. Second, out of an abundance of caution, we would like to monitor further this latest vendor service update and its impacts on secondary nodes before updating primary nodes. Third, we are expecting the availability of a new vendor service update in the coming days or weeks, and we would like to ensure that release notes for this forthcoming update do not reveal any major issues in the current service update. Performance and availability of all database clusters is one of our highest priorities, and we believe this measured approach to the most prudent course of action at this time. As always, we'll continue to monitor all systems and will address any issues if they arise.
May 4, 20:58 EDT