poorbarcode commented on PR #23011: URL: https://github.com/apache/pulsar/pull/23011#issuecomment-2217135544
@merlimat >> a. (Highlight) Issue: the object will always be in `broker-2`'s memory, there is no mechanism to unload it so far. > This should only be while `broker-2` is partitioned from ZK. > * When the broker reconnects, it will discover that the ownership is lost and it will unload the topic So far, it will not unload the topic. I will write a test to reproduce it. >> switch the topic's owner to `broker-2` since it is backed. > Once `broker-2` comes back, the ownership won't come back to `broker-2` since it's already in `broker-0` After a shedding, the bundle may switch to `broker-2` >> b. Issue: the consumers/producers who connected to broker-2 will get a fenced error. >> (Highlight) Issue: the consumers/producers will get a fenced error.... > The clients will get fenced error and then they will re-do the lookup and discover that a different broker is the owner Correct, but the two issues above will lead to the issue can not be recovered. -- 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: commits-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
