Comment 3 for bug 1704404

commit 28b60e8f723ab3d641cf7e14ea24ecad22f2bc9f
Author: Krunal Bauskar <email address hidden>
Date: Fri Aug 11 08:59:51 2017 +0530

    - PXC#850: Inconsistent behavior on data consistency abort

      Problem:
      -------

      Say out of 3 node cluster, 2 nodes leave cluster due to
      data inconsistency then sole pending node should also turn
      non-Primary given that
      a. It doesn't have majority
      b. It is difficult to tell if pending node has good data
         or node that left.

      Currently, if node detects inconsistency then it leaves
      cluster gracefully and depending on timing
      sole pending node can turn non-Primary or Primary.

      Solution:
      --------

      Ensure that node leaving cluster due to data inconsistency,
      first isolate itself from cluster there-by turning non-Primary
      and forcing re-evaluation of quorum on pending nodes.

      This will ensure if minority of the nodes has inconsistent data
      and majority of the nodes are shutting down, miniority will turn non-Primary.

      (If user still would like to operate with minority nodes
       given these are writer nodes or more reliable nodes
       user can pre-adjust the pc.weight to maintain quorum).