Type: Technical Task
Affects Version/s: None
Fix Version/s: 7.0.0 M4
The changes here will revert the changes in
LPS-52578 which removed inetAddres support from ClusterNode. The reason is we need both portal address and bind address, they are used in different scenario:
1) Portal address is the address to access the application server where portal is running
It can be acquired by either configuring properties(like portal.instance.inet.socket.address) in portal.properties or extracting from the first request arrived.
By default, it is configured when the first request arrives, it means it is not available before the first request arrives.
Currently it is only used when loading lucene indexes from cluster.
2) Bind address is the address to access other nodes in cluster
It is set to the bind address of jgroups channel automatically when cluster node is created.
Since each cluster node represents a portal instance in cluster, and each portal instance should have more than one jgroups channels, there are more than one addresses we can use. To make it simple, we just choose the bind address of control channel.
It is used by other functions which depends on cluster, for example the bootstrap of cache from cluster.
The main reason we need bind address is there is portal address might not be available before first request arrives.