Igor, It depends on how address resolver works. But I agree, in general case it's possible that a node can only resolve public address for itself. In such scenario we must publish public addresses in IP finder.
-Val On Mon, Jun 26, 2017 at 1:02 PM, Igor Rudyak <irud...@gmail.com> wrote: > Option 2 also will not work for IaaS environments, where node can > dynamically join or leave cluster. > > Igor > > On Jun 26, 2017 12:12 PM, "Valentin Kulichenko" < > valentin.kuliche...@gmail.com> wrote: > > > Yakov, > > > > Nodes that join outside of the network (usually these are clients) need > to > > know public addresses to connect. To make it work either of these must > > happen: > > > > 1. Server nodes publish their public addresses in IP finder so that > clients > > can use them to connect. > > 2. Client nodes use address resolver to map published internal addresses > to > > public addresses. > > > > Both will work, but frankly I like option 1 more. First of all, it's just > > more intuitive that IP finder contains all possible addresses that can be > > used to join. Second of all, option 2 introduces requirement to have > > address resolver for server addresses configured on client nodes - this > is > > not very good from usability standpoint. > > > > -Val > > > > On Mon, Jun 26, 2017 at 3:17 AM, Yakov Zhdanov <yzhda...@apache.org> > > wrote: > > > > > Guys, I don't get the point. > > > > > > 1. Why addresses processed by address resolver should appear in shared > > > finder? In my understanding finders contain only internal IPs which > > should > > > be processed by a resolver. > > > > > > 2. This one is very critical. Nikolay and Anton, how can I review the > > > changes?! Please update the ticket with PR or commit hash. > > > > > > --Yakov > > > > > >
