I am facing a similar problem, trying to use apache-ignite 2.6.
May be, you can help me.
I set up my discovering using TcpDiscoverySpi and
TcpDiscoveryMulticastIpFinder:
ipFinder.setMulticastGroup(228.10.10.157)
ipFinder.setMulticastPort(10501)
discoverySpi.setLocalPort(10502)
disc
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
wrote:
> Hi Val, Ignite team
>
> Reviewed all opened Ignite
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 622
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/
Thanks Val
one more question on this
if I want to minimize number of potentially-used ports (because of our
security guys)
is it ok to have configuration like below one?
here we have 3 server nodes each running on separate server, they always
use the same 47500 port - no ranges
As I understood if
The only place where Ignite uses UDP is multicast IP finder [1]. Default
number is 47400.
[1]
https://apacheignite.readme.io/docs/cluster-config#multicast-based-discovery
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
what about UDP ports? what they are used for in Ignite?
On Thu, Apr 19, 2018 at 10:40 PM, vkulichenko wrote:
> Most of these seem to ephemeral ports assigned to discovery and
> communication
> clients when they connect to well known configured ports on server side.
> That would always happen fo
Most of these seem to ephemeral ports assigned to discovery and communication
clients when they connect to well known configured ports on server side.
That would always happen for any TCP connection.
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Team,
Coming back to this question with Ignite 2.4.0
Here is what I see in Resource monitor (Windows Server 2012 R2)
Can you comment on these unknown-purpose ports please?
Image PID Address PortProtocol
java.exe3892IPv6 unspecified10800
this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Which-ports-does-ignite-cluster-need-to-run-normally-tp8031p8750.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
ports.
Thanks,
edwardk
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Which-ports-does-ignite-cluster-need-to-run-normally-tp8031p8676.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
is started first.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Which-ports-does-ignite-cluster-need-to-run-normally-tp8031p8364.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
scalability
, do we also need to have to update the ignite-configuration.xml in all the
service(client nodes) and all server nodes too.
Thanks,
voli.sri
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Which-ports-does-ignite-cluster-need-to-run-normally
.70518.x6.nabble.com/Which-ports-does-ignite-cluster-need-to-run-normally-tp8031p8352.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi,
For the joining nodes to cluster, Communication and Discovery SPI will be
inough:
TcpDiscoverySpi:47500~47600
TcpCommunicationSpi:47100~47200
by default.
Others is optinal:
time server port:31100~31200
If you use time synchronization between nodes.
TCP server port:11211
for connect by int
Hi all,
There is an active firewall in my system, and these following ports will be
added to exceptions list.
time server port??31100~31200
TCP server port??11211
Remote Management ??com.sun.management.jmxremote.port49128
TcpDiscoverySpi??47500~47600
TcpCommunicationSpi??47100~47200
shared
16 matches
Mail list logo