Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Pulsar Dashboard Displays Very Little Information

See original GitHub issue

Describe the bug

The pulsar-dashboard does not display the information published by the pulsar cluster.

To Reproduce Steps to reproduce the behavior:

Install a bare metal pulsar
1. on an openstack cloud
2. rather than a DNS server distribute identical /etc/hosts files to each of the vm’s and the development machine
3. 3 zookeeper each on their own vm
4. 3 bookie/broker each pair on their own vm
On the development machine: Git clone the pulsar
1. build the docker image : docker build -t apachepulsar/pulsar-dashboard dashboard 2: export SERVICE_URL=http://ledge2:8080/ 3: docker run -p 80:80 -e SERVICE_URL=$SERVICE_URL apachepulsar/pulsar-dashboard
Construct a
1. single tenant
2. several namespaces
3. several topics

Expected behavior The pulsar-dashboard should show clusters, tenants, namespaces, etc.

Screenshots The pulsar http server shows the presence of the cluster … image(2)

The pulsar-dashboard apparently does not know about the cluster… image(1)

But no if you bring up one of the tabs having a CLUSTERS menu on the right there is the missing cluster…

Desktop (please complete the following information):

OS: Ubuntu 18.04 for the development machine and vm’s

Additional context Because /etc/hosts is used instead of DNS it is necessary to use the ledger2 ipaddr.

 export SERVICE_URL=http://128.60.107.171:8080/

Issue Analytics

State:
Created 4 years ago
Comments:12 (6 by maintainers)

Top GitHub Comments

1reaction

phreedcommented, Apr 14, 2019

The problem is with the name lookup. The messages returned by pulsar contain the urls for other objects. Those url contain host names and the docker image has no way of looking them up. This is easily remedied by changing the way the docker image is run.

docker run --network=host -p 80:80 -e SERVICE_URL=http://ledger2:8080 apachepulsar/pulsar-dashboard

Note the --network=host parameter. In my case this amounts to granting access to the /etc/hosts files. I would think that this would be the recommended way to run pulsar-dashboard in the “getting started” section of the documentation.

0reactions

sijiecommented, Nov 4, 2019

Closed this issue since it was resolved

Top Results From Across the Web

[#PULSAR-2] Pulsar Dashboard Displays Very Little - ASF JIRA

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 ...

TRAC: Walkthrough - From Dashboard to Report | Pulsar Library

Our Custom Dashboards and Reporting system go hand-in-hand to deliver you and your team meaningful reports with as little effort as possible.

[jira] [Created] (PULSAR-2) Pulsar Dashboard Displays Very Little

[jira] [Created] (PULSAR-2) Pulsar Dashboard Displays Very Little ... cluster. pulsar-dashboard is running as a docker container on my desktop computer.

Vicon Pulsar Reference Guide - Documentation

The Lowest Battery Charge indicator shows that the Pulsar with the lowest charge is almost at 0%, ie, almost fully discharged (a Pulsar...

Viewing Pulsar decisions, availability, & performance

You can review this information as a map, a line chart, or a bar chart, all of which display a clear breakdown of...