hzluyang opened a new issue, #15419:
URL: https://github.com/apache/pulsar/issues/15419
pulsar 2.9.2
3 brokers:
4 bookeepers
recently I am testing brokers isolation
But I came across these problems below:
**1 My ns-isolation-policy**
bin/pulsar-admin ns-isolation-policy get appops-pulsar-jdlt ly
{
"namespaces" : [ "luyanghaha/ly" ],
"primary" : [ "appops-pulsar-05.jdlt.163.org:8080" ],
"secondary" : [ "appops-pulsar-06.jdlt.163.org:8080" ],
"auto_failover_policy" : {
"parameters" : {
"min_limit" : "1",
"usage_threshold" : "80"
},
"policy_type" : "min_available"
}
2 lookup topics unavailable I used puslar-perf to produce messages
but fail " Could not get connection to broker:
org.apache.pulsar.client.api.PulsarClientException$LookupException:
{"errorMsg":"No broker was available to own
persistent://luyanghaha/ly/isly-partition-0"
bin/pulsar-admin topics partitioned-lookup persistent://luyanghaha/ly/isly
HTTP 503 Service Unavailable
Reason: javax.ws.rs.ServiceUnavailableException: HTTP 503 Service Unavailable
}
3 if I delete ns-isolation-policy it work correctly
bin/pulsar-admin ns-isolation-policy delete appops-pulsar-jdlt ly
bin/pulsar-admin topics partitioned-lookup persistent://luyanghaha/ly/isly
"persistent://luyanghaha/ly/isly-partition-0
pulsar://appops-pulsar-06.jdlt.163.org:6650"
"persistent://luyanghaha/ly/isly-partition-1
pulsar://appops-pulsar-07.jdlt.163.org:6650"
"persistent://luyanghaha/ly/isly-partition-2
pulsar://appops-pulsar-07.jdlt.163.org:6650"
"persistent://luyanghaha/ly/isly-partition-3
pulsar://appops-pulsar-06.jdlt.163.org:6650"
"persistent://luyanghaha/ly/isly-partition-4
pulsar://appops-pulsar-06.jdlt.163.org:6650"
"persistent://luyanghaha/ly/isly-partition-5
pulsar://appops-pulsar-07.jdlt.163.org:6650"
"persistent://luyanghaha/ly/isly-partition-6
pulsar://appops-pulsar-07.jdlt.163.org:6650"
"persistent://luyanghaha/ly/isly-partition-7
pulsar://appops-pulsar-06.jdlt.163.org:6650"
"persistent://luyanghaha/ly/isly-partition-8
pulsar://appops-pulsar-06.jdlt.163.org:6650"
"persistent://luyanghaha/ly/isly-partition-9
pulsar://appops-pulsar-07.jdlt.163.org:6650"
4 this comand is what I set ns-isolation-policy
bin/pulsar-admin ns-isolation-policy set --auto-failover-policy-type
min_available --auto-failover-policy-params min_limit=1,usage_threshold=80
--namespaces luyanghaha/ly --primary appops-pulsar-05.jdlt.163.org:8080
--secondary appops-pulsar-06.jdlt.163.org:8080 appops-pulsar-jdlt ly
It seems like my ns-isolation-policy is not correct so when i apply the
policy And unload topics/namespaces the pulsar failed to assign topics to
correct broker make command "partitioned-lookup" fail No broker was available
to own .
But I can't figure it out
broker logs didn't show useful messages
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
