Bug #99847 Windows installer 8.0.20 INNODB cluster will fail everytime
Submitted: 11 Jun 2020 9:04 Modified: 11 Jun 2020 10:48
Reporter: damon pillinger Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL for Windows: Installer Severity:S2 (Serious)
Version:8.0.20 OS:Windows (all versions)
Assigned to: MySQL Verification Team CPU Architecture:Any (all)
Tags: INNODB cluster does not open all of the required ports

[11 Jun 2020 9:04] damon pillinger
Description:
Windows installer will now open port 33060 when you use the installer to create an INNODB cluster. (thanks to all involved)

Unfortunately, port 33061 needs to be opened as well for the installed to work and join 2nd (and more) nodes to the cluster.

Port 33060 is shown as the default and IS opened by the installer (given the checkbox is ticked) however 33061 is not.

I am unsure if this is a problem within the installer or an undocumented port. 

I do not believe this is a problem in documentation, there is a checkbox to open the ports on the firewall in the installer and without the above knowledge you would not be able to join an existing cluster.

thanks
Damon

How to repeat:
clean install of windows 10 complete with all updates (11th June 2020)
install first INNODB node

clean install of windows 10 complete with all updates (11th June 2020)
install second INNODB node

It will fail on the last stage and will not join the cluster.

open port 33061 on first node for TCP InBound in the windows Firewall

clean install of windows 10 complete with all updates (11th June 2020)
open port 33061 on this node for TCP InBound in the windows Firewall
install Third INNODB node and it will join the cluster very quickly.

Suggested fix:
open port 33061 on both nodes for TCP InBound in the windows Firewall

recommend : look to see why port 33061 is being used 
a) is it using the selected port (33060) and adding 1 to it?
b) port 33061 is undocumented within the installer but is part of the cloning process joining the cluster.
[11 Jun 2020 10:48] MySQL Verification Team
Duplicate of Bug# 99194