hanguyen6 opened a new issue #10719: URL: https://github.com/apache/pulsar/issues/10719
**Describe the bug** We connect to Pulsar brokers via proxy URL and observe that after Pulsar brokers restart (due to Out-of-Memory) requests for Pulsar schemas return "503 Service Unavailable " or "502 Bad Gateway", sometimes 404 Not found org.apache.pulsar.shade.javax.ws.rs.NotFoundException: HTTP 404 Not Found org.apache.pulsar.shade.javax.ws.rs.ServiceUnavailableException: HTTP 503 Service Unavailable Restart application pod and it was connecting to Pulsar again. Is there a debug mode and where we can check to understand the problem? -- 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]
