You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that the semi-sync log line interprets the server_id as signed 32-bit, whereas the log line from core mysqld interprets it as unsigned (or perhaps signed 64-bit):
It could just be a printing error, but I wouldn't be surprised if this is actually causing the buffer overflow.
When choosing random server_ids, we had assumed we could go up to 2^32-1 because that's what the MySQL docs say. However it appears the semi-sync plugin does not agree, so we should be more conservative and limit ourselves to 2^31-1.
The text was updated successfully, but these errors were encountered:
FYI @rnavarro
Users have seen the semi-sync plugin crash on the master, as mentioned in #2279.
From the MySQL error log:
I noticed that the semi-sync log line interprets the server_id as signed 32-bit, whereas the log line from core mysqld interprets it as unsigned (or perhaps signed 64-bit):
It could just be a printing error, but I wouldn't be surprised if this is actually causing the buffer overflow.
When choosing random server_ids, we had assumed we could go up to 2^32-1 because that's what the MySQL docs say. However it appears the semi-sync plugin does not agree, so we should be more conservative and limit ourselves to 2^31-1.
The text was updated successfully, but these errors were encountered: