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 2022/08/31 12:07:42 UTC
[GitHub] [pulsar] KannarFr commented on pull request #17254: [fix][broker] Fix intermittent issue where leader broker information is lost and causes lookup issues
KannarFr commented on PR #17254:
URL: https://github.com/apache/pulsar/pull/17254#issuecomment-1232850099
To be sure, could this issue result in 502 during topic creation? I just had this problem.
I had these logs on brokers:
```Aug 31 07:30:40 test-pulsar-c2-n1 pulsar-broker[1956320]: 07:30:40.053 [pulsar-2-16] WARN org.apache.pulsar.broker.namespace.NamespaceService - The information about the current leader broker wasn't available. Handling load manager decisions in a decentralized way. NamespaceBundle[customtenant/customns/0xc0000000_0xffffffff]
Aug 31 07:30:40 test-pulsar-c2-n1 pulsar-broker[1956320]: 07:30:40.055 [pulsar-web-34-3] INFO org.eclipse.jetty.server.RequestLog - 192.168.11.6 - - [31/Aug/2022:07:30:40 +0000] "PUT /admin/v2/persistent/customtenant/customns/customtopic?authoritative=false HTTP/1.1" 307 0 "-" "Jetty/9.4.44.v20210927" 5
Aug 31 07:30:40 test-pulsar-c2-n1 pulsar-broker[1956320]: 07:30:40.066 [pulsar-2-4] WARN org.apache.pulsar.broker.namespace.NamespaceService - The information about the current leader broker wasn't available. Handling load manager decisions in a decentralized way. NamespaceBundle[customtenant/customns/0xc0000000_0xffffffff]
Aug 31 07:30:40 test-pulsar-c2-n1 pulsar-broker[1956320]: 07:30:40.068 [pulsar-web-34-9] INFO org.eclipse.jetty.server.RequestLog - 192.168.11.6 - - [31/Aug/2022:07:30:40 +0000] "PUT /admin/v2/persistent/customtenant/customns/customtopic?authoritative=false HTTP/1.1" 307 0 "-" "Jetty/9.4.44.v20210927" 4
Aug 31 07:30:40 test-pulsar-c2-n1 pulsar-broker[1956320]: 07:30:40.079 [pulsar-2-5] WARN org.apache.pulsar.broker.namespace.NamespaceService - The information about the current leader broker wasn't available. Handling load manager decisions in a decentralized way. NamespaceBundle[customtenant/customns/0xc0000000_0xffffffff]
Aug 31 07:30:40 test-pulsar-c2-n1 pulsar-broker[1956320]: 07:30:40.080 [pulsar-web-34-3] INFO org.eclipse.jetty.server.RequestLog - 192.168.11.6 - - [31/Aug/2022:07:30:40 +0000] "PUT /admin/v2/persistent/customtenant/customns/customtopic?authoritative=false HTTP/1.1" 307 0 "-" "Jetty/9.4.44.v20210927" 4
Aug 31 07:30:40 test-pulsar-c2-n1 pulsar-broker[1956320]: 07:30:40.090 [pulsar-2-13] WARN org.apache.pulsar.broker.namespace.NamespaceService - The information about the current leader broker wasn't available. Handling load manager decisions in a decentralized way. NamespaceBundle[customtenant/customns/0xc0000000_0xffffffff]
Aug 31 07:30:40 test-pulsar-c2-n1 pulsar-broker[1956320]: 07:30:40.092 [pulsar-web-34-9] INFO org.eclipse.jetty.server.RequestLog - 192.168.11.6 - - [31/Aug/2022:07:30:40 +0000] "PUT /admin/v2/persistent/customtenant/customns/customtopic?authoritative=false HTTP/1.1" 307 0 "-" "Jetty/9.4.44.v20210927" 4
```
Then nothing related to this customtopic even on another broker. And the response was HTTP 502.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org