So, the solution to this is to add a SST option to use extra_port and use that extra port (after detection of threadpool) with innobackupex like
innobackupex --host --port ..
This will make innobackupex use TCP on extra_port.
Note that, since innobackupex uses mysql just for obtaining status variables. This shouldn't last long or cause any issues.
Moreso, the extra_port is specifically meant for maintenance and/or admn tasks like backups.
Also, it would be recommended to have extra_port set to 2 or more (than default 1), so that while one is being used for backup, the other can be used for logging through client (if necessary).
So, the solution to this is to add a SST option to use extra_port and use that extra port (after detection of threadpool) with innobackupex like
innobackupex --host --port ..
This will make innobackupex use TCP on extra_port.
Note that, since innobackupex uses mysql just for obtaining status variables. This shouldn't last long or cause any issues.
Moreso, the extra_port is specifically meant for maintenance and/or admn tasks like backups.
Also, it would be recommended to have extra_port set to 2 or more (than default 1), so that while one is being used for backup, the other can be used for logging through client (if necessary).