"Protocol violation. JOIN message sender ... is not in state transfer (SYNCED). Message ignored." with concurrent IST

Bug #1379792 reported by Philip Stoev
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Invalid
Undecided
Unassigned
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC
Status tracked in 5.6
5.5
Invalid
Undecided
Unassigned
5.6
Invalid
Undecided
Unassigned

Bug Description

A test that performs concurrent IST with two joiners and one donor, produces semi-reliably with the following warning:

2014-10-10 16:37:31 19225 [Warning] WSREP: Protocol violation. JOIN message sender 0.0 (localhost.localdomain) is not in state transfer (SYNCED). Message ignored.

Revision history for this message
Philip Stoev (philip-stoev-f) wrote :
Revision history for this message
Philip Stoev (philip-stoev-f) wrote :

Attaching a test case. Please unpack in mysql-test and run:

 perl mysql-test-run.pl --suite galera_3nodes galera_simultaneous_ist --big-test

summary: - "Protocol violation. JOIN message sender 0.0 (localhost.localdomain) is
- not in state transfer (SYNCED). Message ignored." with concurrent IST
+ "Protocol violation. JOIN message sender ... is not in state transfer
+ (SYNCED). Message ignored." with concurrent IST
Revision history for this message
Teemu Ollakka (teemu-ollakka) wrote :
Revision history for this message
Alex Yurchenko (ayurchen) wrote :

or, rather, https://github.com/codership/galera/issues/106, cause all work is done there

Philip, does it happen with 106 branch?

Revision history for this message
Philip Stoev (philip-stoev-f) wrote :

Yes, I believe the gh106 branch is also affected . I will retest on Monday. Also, Yan told me that the master and the gh106 branch are currently identical.

Revision history for this message
Philip Stoev (philip-stoev-f) wrote :

For some reason, I can no longer reproduce it on gh106. It is still reproducible on master.

If you feel that this bug is therefore a dead end, please close it when gh106 is pushed.

Changed in codership-mysql:
status: New → Confirmed
Revision history for this message
Raghavendra D Prabhu (raghavendra-prabhu) wrote :

@Phillip,

Is this reproduceable with master now?

Revision history for this message
Philip Stoev (philip-stoev-f) wrote :

The warning is now:

2014-12-15 10:53:26 63468 [Warning] WSREP: SYNC message from member 0 in non-primary configuration. Ignored.

Revision history for this message
Philip Stoev (philip-stoev-f) wrote :

Teemu reports that the warning currently produced by the test requires further investigation.

Revision history for this message
Philip Stoev (philip-stoev-f) wrote :

The new warning is now

https://github.com/codership/galera/issues/204

I am closing this ticket because the previous warning is no longer reproducible.

Changed in codership-mysql:
status: Confirmed → Invalid
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1752

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.