hi, +1
Furthermore, for consistency and to handle similar network topology needs for other nodes, I also support adding a corresponding `cn_internal_bind_address` configuration for CNs. and `ain_internal_bind_address` for AINode? --------------------------- Xuan Wang On 2025/11/06 06:10:19 Yuan Tian wrote: > Hi all, > > I think we need a new configuration named `dn_internal_bind_address` which > is used for DN to bind and only listen to the port of that address. > > The reason we need to add this configuration item is that there’s a type of > cross-region cluster setup where users deploy two DN nodes of the same > cluster in different data centers. Machines in different data centers can > only communicate through their public IPs (via NAT routing), but each > machine itself cannot directly listen on a public IP port — it can only > bind to its internal (private) IP. > > Currently, we only have a single configuration named `dn_internal_address` > which is used both for the IP that *DN-1* (server-side) binds to and for > the IP that *DN-2* (client-side) uses to connect. > > I think we should keep the `dn_internal_address` for > another-dn-connect-to-ip usage and add another new configuration named > `dn_internal_bind_address` for dn-bind-to-ip usage. > > > Best regards, > > ----------------------- > > Yuan Tian >
