youurayy edited a comment on issue #6002: 2.4.2 pulsar dashboard cannot view a message URL: https://github.com/apache/pulsar/issues/6002#issuecomment-571997573 @jiazhai yes happens each time. Steps: 1. install pulsar 2.4.2 from the Helm Chart (I use Helm 3) - note: To get 2.4.2 working on Kubernetes, do the following workarounds: - turn off functions #5818 - change the image spec for the Dashboard to 2.4.1 due to #5847 - check if admin api works on all proxy pods, and restart those which are stuck #5994 2. create a tenant and a namespace - note: I create my namespace with: - `bin/pulsar-admin namespaces set-backlog-quota mytenant/mynamespace --limit 300M --policy consumer_backlog_eviction` - `bin/pulsar-admin namespaces set-deduplication mytenant/mynamespace --enable` 3. publish some messages into a persistent topic in that namespace - note: I use Protobuf serliaization; I don't use message compression at this time 4. go to the Dashboard, navigate to the topic, and try to view some messages currently residing on that topic - on the Dashboard webpage, when clicking on a message, nothing visible will happen (just a brief display of a loading indicator) - you have to open e.g. the Chrome web dev tools and look at Console or Network to see the 500 error returned
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
