We have a SQL Server 2016 two node alwayson group, when we do a failover, the new secondary database changed to reverting/ in recovery state, this is understandable since there are long transactions which needs to be rolled back when fails over,
however, during this time, read-only applications still tries to connected to the new secondary, but failed to open the database, this is not expected. Since the database is not synchronizing, shouldn't the connections be directed to the new primary node?
↧