Comment 4 for bug 1629566

This issue got introduced while our desync_count logic was replaced by upstream desync_count logic which caused inconsistency in PXC.

It has been solved in 5.6.32.

---------------

I verified that 5.6.30 we hit the issue and also that 5.6.32 doesn't hit the issue.

Related checkin:

commit 4579c434498eaaff1feb40ece7b8dfad01b31915
Merge: b0a8801 c51109c
Author: Krunal Bauskar <email address hidden>
Date: Mon Aug 15 12:22:59 2016 +0530

    Merge pull request #80 from natsys/3.x-pxc-665

    - #PXC-665: SST donor node has status "JOINED" after successful resync

commit c51109c44cb39c94cfa9644334a810d3aeee66d2
Author: Julius Goryavsky <email address hidden>
Date: Fri Aug 12 19:34:08 2016 -0400

    - #PXC-665: SST donor node has status "JOINED" after successful resync

    Operations that use the global lock (such as FLUSH TABLES FOR READ LOCK) and DDL operations that are protected via the RSU can be performed during SST. At the same time, they come in
to interference with the SST process, which leads to a variety of errors, including hang or crash of the donor node after SST donation. Alternatively, the SST donor node stays in the "JO
INED" status, even after the completion of the SST.