michaeljmarshall commented on issue #13363: URL: https://github.com/apache/pulsar/issues/13363#issuecomment-1082599037
@suiyuzeng - you mention that you're running 2.8.2, but that version wasn't released when you opened this issue. Can you double check which version of broker and client where you're seeing this issue? Also, which client are you using (java, go, python, etc.)? > In client, it seems there is some problem about the network. Close the connection and retry. But the server send the error "Producer is already connected to topic" for earch retry. @lhotari observed this behavior and fixed a race condition just this week: https://github.com/apache/pulsar/pull/13428. That patch won't be live until 2.8.3. > 2021-12-14 15:11:07 The server receive the registe info from the port 34398 for the first time. 2021-12-14 15:54:45 get the new connection from the same client with the port of 34172, and registe the same producer. Is it possible that you're creating two producers with the same name? > There is a possibility that a exception is threw in org.apache.pulsar.common.protocol.PulsarHandler#handleKeepAliveTimeout. Then the schedule task will not run any more as there is no exeception catch. "ctx.writeAndFlush" may throw some RuntimeException as there is some problem about the network. This is solved by https://github.com/apache/pulsar/pull/12853, which will be included in 2.8.2. Now that 2.8.3 has been released, are you able to test using the latest version to see if the issue is still present? -- 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]
