{"push_id":1250459826,"size":1,"distinct_size":1,"ref":"refs/heads/5.6-pxc-665","head":"b5f6c18398e231efc7527f21ecef0ed32df71bdb","before":"214c798ead9ca0c099784dff969034b8504dbdd7","commits":[{"sha":"b5f6c18398e231efc7527f21ecef0ed32df71bdb","author":{"name":"Julius Goryavsky","email":"18f7161cd8c950d81f2c0c29770532d6dbbeb9a7@gmail.com"},"message":"- #PXC-665: SST donor node has status \"JOINED\" after successful resync\n\nOperations 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. In this case, they come into interference with the SST process, which leads to a variety of bugs, including hang or crash of the donor node after SST donation. Alternatively, the SST donor node stays in the \"JOINED\" status, even after the completion of the SST.\n\nThis patch solves the problem with the incorrect classification of the \"JOIN\" message (which is generated as response to the wsrep->resync() call) at the GCS layer. Improper handling of the JOIN message leads to ignoring of the subsequent SYNC message and generates the above-described problems.\n\nPausing of the RSU operations during the SST will be solved as a separate issue in another patch.","distinct":true,"url":"https://api.github.com/repos/natsys/percona-xtradb-cluster/commits/b5f6c18398e231efc7527f21ecef0ed32df71bdb"}]}
{"actor":{"display_login":"sysprg"}}