Yes, but it shouldn't have been. One node of the DB cluster puked when it ran out of disk. This isn't an issue normally, as that's the point of having a cluster. However, Then another node went offline to do backups. The cluster assumed it was split brain and locked itself. Would've been back online sooner but I had to figure out the order of events to determine which node to bring online first.