mesh-seed-address-port 10.8.40.54 3002
does following bind operations for port 3002
tcp 0 0 10.8.40.53:3002 0.0.0.0:* LISTEN 22698/asd
tcp 0 0 10.8.40.53:3002 10.8.40.52:39183 ESTABLISHED 22698/asd
with mentioned parameter it does same. Without
address it binds port defined by service.
tcp 0 0 10.8.40.51:3002 0.0.0.0:* LISTEN 25063/asd
Data are still going through eth0 (RX 609.1 GB; TX 2.3 TB), eth1 (RX 3.4 MB; TX 492.0 B) is completely untouched even doc says that port is used for Intra-cluster communication (migrates, replication, etc).
Test case: Node A is under load and Node B is down, once Node A has all data loaded Node B become to be available for replication test.