You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Olexandr K <ol...@gmail.com> on 2018/05/07 10:03:18 UTC
Re: Which ports does ignite cluster need to run normally?
Hi Val, Ignite team
Reviewed all opened Ignite ports after your comments.
Everything is clear except loopback-related ports.
Here is what I see in Resource Monitor (Windows Server 2012 R2)
(prunsrv.exe is common-daemon java service wrapper running JVM 1.8 inside)
I don't understand what port 62219 is used for.
I exprimented with Ignite restarts and see that this port is chosen
dynamically.
Also, if we have port 62219 opened, we also observe number of loopback
connections starting from port 62222
What are all these loopback connections used for?
Can we disable this or at least configure to use static ports?
<server1>
Listening ports
Image PID Address Port Protocol
Firewall Status
prunsrv.exe 2220 IPv4 unspecified 62219 TCP Allowed,
restricted - ???
prunsrv.exe 2220 IPv4 unspecified 47500 TCP Allowed,
restricted - Ignite discovery
prunsrv.exe 2220 IPv4 unspecified 47100 TCP Allowed,
restricted - Ignite communication
prunsrv.exe 2220 IPv4 unspecified 11211 TCP Allowed,
restricted - HTTP internal
prunsrv.exe 2220 IPv4 unspecified 10800 TCP Allowed,
restricted - ODBC
prunsrv.exe 2220 IPv4 unspecified 9020 TCP Allowed,
restricted - JMX
TCP Connections
Image PID Local Address Local Port Remote Address Remote
Port Packet Loss (%) Latency (ms)
prunsrv.exe 2220 server1_host 47500 visor_host 57550 0
10
prunsrv.exe 2220 server1_host 50607 server2_host 47100
0 1
prunsrv.exe 2220 server1_host 62275 server2_host 47500
0 1
prunsrv.exe 2220 IPv4 loopback 62230 IPv4 loopback 62231
0 0
prunsrv.exe 2220 IPv4 loopback 62251 IPv4 loopback 62250
- -
prunsrv.exe 2220 IPv4 loopback 62250 IPv4 loopback 62251
- -
prunsrv.exe 2220 IPv4 loopback 62249 IPv4 loopback 62248
- -
....
On Thu, Apr 26, 2018 at 8:42 PM, vkulichenko <va...@gmail.com>
wrote:
> Hi,
>
> The configuration is fine and it does eliminate ranges so that node always
> binds to 47500. The only drawback is that if 47500 is not available for
> whatever reason, node would not start.
>
> -Val
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
Re: Which ports does ignite cluster need to run normally?
Posted by Olexandr K <ol...@gmail.com>.
It looks like that port is not related to Ignite but JVM opens several
ports for JMX
Described here:
https://stackoverflow.com/questions/20884353/why-java-opens-3-ports-when-jmx-is-configured
On Mon, May 7, 2018 at 1:03 PM, Olexandr K <ol...@gmail.com>
wrote:
> Hi Val, Ignite team
>
> Reviewed all opened Ignite ports after your comments.
> Everything is clear except loopback-related ports.
>
> Here is what I see in Resource Monitor (Windows Server 2012 R2)
> (prunsrv.exe is common-daemon java service wrapper running JVM 1.8 inside)
>
> I don't understand what port 62219 is used for.
> I exprimented with Ignite restarts and see that this port is chosen
> dynamically.
> Also, if we have port 62219 opened, we also observe number of loopback
> connections starting from port 62222
> What are all these loopback connections used for?
> Can we disable this or at least configure to use static ports?
>
> <server1>
>
> Listening ports
>
> Image PID Address Port Protocol
> Firewall Status
> prunsrv.exe 2220 IPv4 unspecified 62219 TCP Allowed,
> restricted - ???
> prunsrv.exe 2220 IPv4 unspecified 47500 TCP Allowed,
> restricted - Ignite discovery
> prunsrv.exe 2220 IPv4 unspecified 47100 TCP Allowed,
> restricted - Ignite communication
> prunsrv.exe 2220 IPv4 unspecified 11211 TCP Allowed,
> restricted - HTTP internal
> prunsrv.exe 2220 IPv4 unspecified 10800 TCP Allowed,
> restricted - ODBC
> prunsrv.exe 2220 IPv4 unspecified 9020 TCP Allowed,
> restricted - JMX
>
> TCP Connections
>
> Image PID Local Address Local Port Remote Address Remote
> Port Packet Loss (%) Latency (ms)
> prunsrv.exe 2220 server1_host 47500 visor_host 57550 0
> 10
> prunsrv.exe 2220 server1_host 50607 server2_host 47100
> 0 1
> prunsrv.exe 2220 server1_host 62275 server2_host 47500
> 0 1
>
> prunsrv.exe 2220 IPv4 loopback 62230 IPv4 loopback 62231
> 0 0
> prunsrv.exe 2220 IPv4 loopback 62251 IPv4 loopback 62250
> - -
> prunsrv.exe 2220 IPv4 loopback 62250 IPv4 loopback 62251
> - -
> prunsrv.exe 2220 IPv4 loopback 62249 IPv4 loopback 62248
> - -
> ....
>
>
> On Thu, Apr 26, 2018 at 8:42 PM, vkulichenko <
> valentin.kulichenko@gmail.com> wrote:
>
>> Hi,
>>
>> The configuration is fine and it does eliminate ranges so that node always
>> binds to 47500. The only drawback is that if 47500 is not available for
>> whatever reason, node would not start.
>>
>> -Val
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>
>
>