tillrohrmann commented on issue #11284: [FLINK-15911][runtime] Make Flink work with NAT. URL: https://github.com/apache/flink/pull/11284#issuecomment-602514974 > @tillrohrmann, I have addressed your comments. > > However, I'm still trying to understand how the following is a common need. > > > What we actually need is that for a given TM `t` all other TMs `t'` can resolve the address of `t`. > > I find it not natural to simulate the above scenario with Docker in the e2e test. For each container I have to manually add the hostname-ip entries of all other containers except for itself. > > Say all the JM and TMs are running in Docker containers. If a given TM `t` cannot resolve its own external address from inside the container, then unless specifically configured like I did in the e2e test, how could the JM and all the other TMs `t'`, which are also inside containers, resolve the address of `t`? If `t'` can resolve the address of `t` by using the same DNS settings as its host, then shouldn't `t'` also use the same DNS settings as its host and be able to resolve its own address? I would assume that in most setups every `t` would be able to resolve all of the others `t'` addresses and also its own. But this is a stronger assumption than saying every `t'` needs to be able to resolve 't' address and hence it breaks some setups (as people complained on the ML/SO).
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
