I was troubleshooting why peers show as "Pending" often in the cluster master web UI. In troubleshooting I ran 'ss |less' and via tcp I found the master connecting on odd ports and vice versa. Heres a "sanitized" example:
Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port
tcp ESTAB 0 0 172.indexercluster.master.ip:8089 172.indexercluster.member.06:41346
tcp ESTAB 0 0 172.indexercluster.master.ip:8089 172.indexercluster.member.04:47714
tcp ESTAB 0 0 172.indexercluster.master.ip:40738 172.indexercluster.member.015:8089
tcp ESTAB 0 0 172.indexercluster.master.ip:53218 172.indexercluster.member.010:8089
tcp ESTAB 0 0 172.indexercluster.master.ip:57761 172.indexercluster.member.018:8089
tcp ESTAB 0 0 172.indexercluster.master.ip:60002 172.indexercluster.member.012:8089
tcp ESTAB 0 0 172.indexercluster.master.ip:54722 172.indexercluster.member.021:8089
tcp ESTAB 0 0 172.indexercluster.master.ip:57434 172.indexercluster.member.014:8089
tcp ESTAB 0 0 172.indexercluster.master.ip:8089 172.indexercluster.member.010:40392
tcp ESTAB 0 0 172.indexercluster.master.ip:57484 172.indexercluster.member.014:8089
tcp ESTAB 0 0 172.indexercluster.master.ip:8089 172.indexercluster.member.018:39212
tcp ESTAB 0 0 172.indexercluster.master.ip:44492 172.indexercluster.member.013:8089
Is this normal communication or something strange?
Not sure I've noticed this before so I wanted to see if anyone else has seen this.
Thanks
↧