harissecic commented on issue #8904: URL: https://github.com/apache/pulsar/issues/8904#issuecomment-743028197
> @harissecic > > I didn't use Azure App Service before. But Pulsar client periodically sends heartbeats to brokers to detect if a connection is broken or not. Then it will automatically reconnect if it detects connections are broken. > > See http://pulsar.apache.org/api/client/2.7.0-SNAPSHOT/org/apache/pulsar/client/api/ClientBuilder.html#keepAliveInterval-int-java.util.concurrent.TimeUnit- This was not the case in my services. However it could have been that the App Service didn't have configuration called Always ON enabled. In this case there's no way that heartbeat would work, yet service would work if one would to make a HTTP request like GET on REST service. Now I don't fully understand what's happening in them but I will try to debug this with Always ON enabled and disabled. check the behaviour. I'm guessing it's most likely that the Always ON was by disabled and in such case I expect it not to work as Azure will shutdown service if there's no trafick going through. However this again raises the question shouldn't heartbeat from Pulsar keep this service running regardless of that feature because Pulsar would be the one sending network traffic? It will take a bit more time for me to make a test environment with Pulsar and a Java client to test this out and report back. I can assume also that it might be Azure killing off those connections for some reason like: n ot having web port active will shut down app regardless of other connections. Whatever it may be this is 99.9% on Azure side and a workaround would be helpful or it may be that the App Service should be avoided. ---------------------------------------------------------------- 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]
