Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
Pulsar is running on an openstack cloud with three vm's in a cluster and the pulsar-zookeeper running on a three node cluster.
pulsar-dashboard is running as a docker container on my desktop computer.
Host name resolution is done via /etc/hosts files on all of the vm's except the docker container. This necessitates setting export SERVICE_URL=http://129.59.107.171:8080/ for the host name .Pulsar is running on an openstack cloud with three vm's in a cluster and the pulsar-zookeeper running on a three node cluster. pulsar-dashboard is running as a docker container on my desktop computer. Host name resolution is done via /etc/hosts files on all of the vm's except the docker container. This necessitates setting export SERVICE_URL= http://129.59.107.171:8080/ for the host name .
Description
It is major for pulsar-dashboard.
I am working with https://github.com/apache/pulsar/tree/v2.3.0 connecting to a pulsar 2.3.0 cluster.
The single pulsar cluster is "pulsar-cluster-1" as you can see from image(2).png.
In image(1).png you can see that the cluster tab would seem to indicate that there are not clusters.
However in image.png you can see that indeed there is a cluster and we are connected to the pulsar server.
