mattisonchao commented on PR #21030: URL: https://github.com/apache/pulsar/pull/21030#issuecomment-1687277935
From my understanding now. It should be a problem like a dirty reading. Right? Since the design of the topic policy mechanism is the final consensus, it's a little bit hard for us to fix this kinda situation. IMO, we can try to define a redirect logic here. 1. non-partitioned topic policy redirect to owner broker. 2. partitioned topic policy redirects to the `partition-0`'s owner broker as a logical topic leader. Afterwards, we move a distributed problem to a single machine which will be easier for us to handle it. - Defining a `sync` method to let the reader read the end of the topic at that moment is better than saving the operation future everywhere from my point of view. -- 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]
