We have a three node Always On Availability Group cluster. We normally patch the passive nodes (N2, N3), fail over from N1 to N2, patch N1, and then fail back to N1. N1 and N2 are sync, N3 is async.
I am in a argument with our colleagues on weather to fail back to node 1 after patching. My colleagues say we have to do this, so that we make sure Node 1 is functional. I am of the opinion that we keep SQL Server on N2 so that we avoid another interruption of failing over to N1.
I was wondering if the practice of failing back to N1 to make sure the node is healthy is warranted or just useless?