What we prototyped was configuring via spring the list of IPs to ignore, because a given installation seemed to have a constant address for the bridge network, and this approach was reliable, once you know the bridge IPs.
When the container starts, you get a list of IP addresses from the kernel. At that point it is impossible to know from inside the container which of those addresses can be used by other ignite nodes, at least without external information. Similarly, if I have an AWS instance I am wondering On Tue, Nov 20, 2018 at 2:08 PM Alexey Goncharuk <alexey.goncha...@gmail.com> wrote: > Hi David, > > This is something we have also encountered recently and I was wondering how > this can be mitigated in a general case. Do you know if an application can > detect that it is being run in a docker container and add the corresponding > list of bridge IPs automatically on start? If so, I this we can add this to > the Ignite so that it works out of the box. > > --AG > > > вт, 20 нояб. 2018 г. в 19:58, David Harvey <syssoft...@gmail.com>: > > > We see some annoying behavior with S3 discovery because Ignite will push > to > > the discovery S3 bucket the IP address of the local docker bridge network > > (172.17.0.1) in our case. Basically, each node when coming online tries > > that address first, and has to go through a network timeout to recover. > > > > To address this, have prototyped a simple extension to > TcpCommunicationSpi > > to allow configuration of a list of IP addresses that should be > completely > > ignored, and will create a ticket and generate a pull request for it. > > > > If there is a better approach, please let us know. > > > > Thanks > > Dave Harvey > > >
