MySQL Bugs: #92686: Mysql server 8.0.12 group replication

Bug #92686	Mysql server 8.0.12 group replication
Submitted:	5 Oct 2018 12:46	Modified:	17 Jan 16:22
Reporter:	lionel mazeyrat	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: Group Replication	Severity:	S2 (Serious)
Version:	8.0.12	OS:	Any
Assigned to:	Bogdan Kecman	CPU Architecture:	Any

Description:
3 Mysql 8.0.12 win server 2016 - GR cluster.
3 nodes are online.

When a restart the service of the R/W node, another go R/W, but the restarted node keep the (MISSING) status.

I've tried to resart it again, the node is still in (MISSING) status.

How to repeat:
3 Mysql 8.0.12 win server 2016 - GR cluster.
3 nodes are online.

When a restart the service of the R/W node, another go R/W, but the restarted node keep the (MISSING) status.

I've tried to resart it again, the node is still in (MISSING) status.

Hi,
I need to see your config files, how exactly did you setup the cluster on windows.

all best
Bogdan

my.ini server 1

Attachment: my1.ini (application/octet-stream, text), 13.80 KiB.

my.ini server 2

Attachment: my2.ini (application/octet-stream, text), 13.78 KiB.

my.

Attachment: my3.ini (application/octet-stream, text), 13.77 KiB.

my.ini server 3

Attachment: my3.ini (application/octet-stream, text), 13.77 KiB.

Hi,

I'm testing this on Windows and on Linux with 8.0.13 and I cannot reproduce the issue you are referring to. In what way you "restart service" on these boxes? 

Thanks
Bogdan

thanks
I will upgrade to 8.0.13 as soon as possible and test again.

Hi,

Thanks for retesting with 8.0.13, now I don't see anything in the release info that suggest anything relevant to this issue is changed there but still.. In the meantime please let me know the answer to "how do you exactly restart the service" so I can retest on my end again.

thanks
Bogdan

The mysql service was restarted from the windows services control pop-up with a stop and then start command.

The mysql service was restarted from the windows services control pop-up with a stop and then start command.

check your configuration file. I have not found the group_replication related configuration

Hi,
Sorry for the late reply, I was unavailable for a while there.

The config files does not correlate with your report. With normal replication this makes no sense, with group replication - regular config I can't reproduce your problem, so I assume this is "configuration" issue that you should solve by contacting support team.

I'm closing as not-a-bug for now but if you can provide a reproducible test case showing this is a bug please feel free to reopen or create a new one.

Best regards
Bogdan