ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kristian Rosenvold <krosenv...@apache.org>
Subject Re: Tcp discovery with clustered docker nodes
Date Thu, 12 May 2016 13:26:30 GMT
To ny understanding no; the java process running innside the docker
container has no possibility of binding to the externally visible ip/port.

Kristian
12. mai 2016 3.22 p.m. skrev "Alexei Scherbakov" <
alexey.scherbakoff@gmail.com>:

> Hi,
>
> TcpDiscoverySPI has two properties(localAddress and localPort), which
> allows you to set local address and port for Discovery SPI to bind.
> T
> Does it solve your problem?
>
>
> .
>
>
> 2016-05-12 10:56 GMT+03:00 Kristian Rosenvold <krosenvold@apache.org>:
>
>> We have been using jdbc based discovery successfully, but have been
>> trying to get this to work with docker. The problem is of course that all
>> the internal IP's inside the docker container are useless, so we'd really
>> need some way to override the discovery mechanism. Now you could of course
>> say that I should be using the static mechanism, but configuration-wise it
>> makes things really messy.
>>
>> It would be much cleaner to simply make each node publish its "correct"
>> external address to the discovery api, so that the JDBC discovery mechanism
>> would contain only the external address (ignoring loopbacks here, unsure if
>> there is a use case).
>>
>> By reading the source it would appear that this is not really supported,
>> or am I missing something ? (It would appear like I need some kind of
>> ovverride in the TcpDiscoveryMulticastIpFinder#initializeLocalAddresses/
>> U.resolveLocalAddresses
>> area).
>>
>>
>> Kristian
>>
>>
>>
>>
>
>
> --
>
> Best regards,
> Alexei Scherbakov
>

Mime
View raw message