You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2021/03/23 17:38:26 UTC
[GitHub] [pulsar] DonHaul opened a new issue #10018: pulsar admin not acessing bookies
DonHaul opened a new issue #10018:
URL: https://github.com/apache/pulsar/issues/10018
Hello I am trying to look at a message on the ledgers via the admin command of the pulsar client:
```/bin/pulsar-admin topics get-message-by-id persistent://public/default/testtopic9 -l 4 -e 3``` however it doesnt wor returning the following error:
````
null
Reason: java.util.concurrent.CompletionException: org.apache.pulsar.client.admin.internal.http.AsyncHttpConnector$RetryException: Could not complete the operation. Number of retries has been exhausted. Failed reason: pulsar-broker-3.pulsar-broker.pulsar.svc.cluster.local
````
I've done ```bin/pulsar-admin brokers list``` and it returns all bookies as expected:
```
"pulsar-broker-0.pulsar-broker.pulsar.svc.cluster.local:8080"
"pulsar-broker-1.pulsar-broker.pulsar.svc.cluster.local:8080"
"pulsar-broker-2.pulsar-broker.pulsar.svc.cluster.local:8080"
"pulsar-broker-3.pulsar-broker.pulsar.svc.cluster.local:8080"
```
I have also verified that that ledfer id and entry exist using the reader api.
I am running this on kubernetes via minikube and I installed using the the helm chart for with 1 replica of each, but changed it the replicas from 1 to 4:, https://github.com/apache/pulsar-helm-chart/blob/master/examples/values-minikube.yaml .
Other than that all configurations remain unchanged.
--
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:
users@infra.apache.org
[GitHub] [pulsar] DonHaul commented on issue #10018: pulsar admin not acessing bookies
Posted by GitBox <gi...@apache.org>.
DonHaul commented on issue #10018:
URL: https://github.com/apache/pulsar/issues/10018#issuecomment-805691547
That was it, I was connecting directy to the broker service instead of to the proxie's webservice webServiceUrl
--
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:
users@infra.apache.org
[GitHub] [pulsar] zymap commented on issue #10018: pulsar admin not acessing bookies
Posted by GitBox <gi...@apache.org>.
zymap commented on issue #10018:
URL: https://github.com/apache/pulsar/issues/10018#issuecomment-805397458
The request looks like redirected to another broker. Can you try with pulsar proxy? You can expose the proxy port on local and use pulsar-admin to connect proxy then execute that command.
--
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:
users@infra.apache.org
[GitHub] [pulsar] DonHaul closed issue #10018: pulsar admin not acessing bookies
Posted by GitBox <gi...@apache.org>.
DonHaul closed issue #10018:
URL: https://github.com/apache/pulsar/issues/10018
--
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:
users@infra.apache.org