JMX is disabled by ManagedUtil: 2023-06-06 14:56:48,384 [myid:] - INFO [main:ManagedUtil@47] - Log4j 1.2 jmx support not found; jmx disabled.
Hence I don't see the 9010 tcp port bound. But why would a random ephemeral port still open? Important that this port is random and keeps changing at every startup. Andor On Tue, 2023-06-06 at 15:08 +0200, Enrico Olivelli wrote: > Andor, > > Il giorno mar 6 giu 2023 alle ore 14:59 Andor Molnar > <an...@apache.org> ha scritto: > > Hi folks, > > > > I cannot find an answer for this which annoys the hell out of me. > > Please help to understand why ZooKeeper is binding a local > > ephemeral > > port right after start without any quorum or client socket opened. > > This > > is what I see when start a 3.4 or 3.5 server is standalone mode. > > (Same > > behaviour is observed with quorum too) > > > > $ bin/zkServer.sh start-foreground > > ZooKeeper JMX enabled by default > > Using config: /home/andor/git/my-zookeeper/bin/../conf/zoo.cfg > > 2023-06-06 14:56:48,378 [myid:] - INFO [main:QuorumPeerConfig@154] > > - > > Reading configuration from: /home/andor/git/my- > > zookeeper/bin/../conf/zoo.cfg > > ... > > 2023-06-06 14:56:48,648 [myid:] - INFO [main: > > NIOServerCnxnFactory@689] > > - binding to port 0.0.0.0/0.0.0.0:2181 > > > > ZooKeeper is running with PID 57126. Admin server is disabled. > > > > $ sudo netstat -plnt | grep 57126 > > tcp6 0 0 > > :::2181 :::* LISTEN 57126/j > > ava > > tcp6 0 0 > > :::45669 :::* LISTEN 57126/j > > ava > > > > What is the second line?? > > It should be JMX > > Enrico > > > Thanks, > > Andor > > > > > >
