aweiri1 commented on issue #24819: URL: https://github.com/apache/pulsar/issues/24819#issuecomment-3429605954
@lhotari we have not yet moved to upgrading our kubernetes pulsar clusters, but plan to soon. In the meantime, I am doing more testing on the issue. I decided to try a bare-metal deployment on my VMs to see if I came across the same topic replication issue. This was a very simple one-node pulsar v4.0.4 cluster deployment (x2) with a global config store (3 VMs total). There is no proxy or load balancer being used, and I did not enable functions. When configuring and testing geo-replication on the bare-metal set up, I started a producer on cluster 1 which auto created the topic on cluster 1. It began sending consistent messages, and after only sending ~5 messages (without starting any consumers) the topic existed on cluster 2 and I was able to view the topic stats. This tells me it could be a kubernetes deployment issue rather than a version issue, but I'm not sure what in the K8s cluster would cause this error.. Wondering if you have any feedback? -- 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]
