zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Norbert Kalmar <nkal...@cloudera.com.INVALID>
Subject Re: zookeeper services are not up when install using helm
Date Thu, 13 Jun 2019 17:49:31 GMT
Hi,

Looks like the port for JMX - 1099 - is already used by another process.
Just change the port, or disable remote JMX (which is a good thing to do
security wise BTW).

Regards,
Norbert

On Thu, Jun 13, 2019 at 6:53 PM Taranisen Mohanta <tmohanta@gmail.com>
wrote:

> I am trying to install the incubator/zookeeper using helm chart on the AWS
> EKS cluster.
> The zookeeper services are not starting on the pods
> Anyone can help me on this.
> $ kubectl get pods
> NAME             READY   STATUS    RESTARTS   AGE
> zm-zookeeper-0   1/1     Running   0          18m
> zm-zookeeper-1   1/1     Running   0          17m
> zm-zookeeper-2   1/1     Running   0          16m
> $ kubectl get service
> NAME                    TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)
>                    AGE
> kubernetes              ClusterIP   10.100.0.1      <none>        443/TCP
>                    7d3h
> zm-zookeeper            ClusterIP   10.100.52.213   <none>        2181/TCP
>                     18m
> zm-zookeeper-headless   ClusterIP   None            <none>
>  2181/TCP,3888/TCP,2888/TCP   18m
> $ kubectl exec zm-zookeeper-2 -- /opt/zookeeper/bin/zkServer.sh
> start-foreground;
> ZooKeeper JMX enabled by default
> ZooKeeper remote JMX Port set to 1099
> ZooKeeper remote JMX authenticate set to false
> ZooKeeper remote JMX ssl set to false
> ZooKeeper remote JMX log4j set to true
> Using config: /opt/zookeeper/bin/../conf/zoo.cfg
> Error: Exception thrown by the agent : java.rmi.server.ExportException:
> Port already in use: 1099; nested exception is:
>     java.net.BindException: Address already in use (Bind failed)
> command terminated with exit code 1
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message