heesung-sn commented on PR #23144: URL: https://github.com/apache/pulsar/pull/23144#issuecomment-2278233827
Internal topics ownership conflict is concern here when the leadership changes frequently - we should make sure only the current leader owns these internal topics. The persistent internal topic can self-resolve this topic ownership conflict by the ledger fencing logic. However, I think the non-persistent internal topics can be problem because the fencing logic doesn't apply to non-persistent topics. To gracefully release the previous ownership of these internal topics, I think we better make followers explicitly close the internal topics - when leadership changes, there might be a chance that some clients reconnect to the old leader if the connected zk and the old leader's zk are slow. Then, when the old leader zk catches up(notifies a follower signal to the old leader), the old leader should make sure to close any internal topics and its client connections, if any. -- 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]
