bsideup commented on issue #5278: Fixed reader cursor seek with disconnection URL: https://github.com/apache/pulsar/pull/5278#issuecomment-577162043 Hi @tuteng & @sijie, Thanks for the ping! > Can you clarify what do you observe "it causes the other connections to disconnect"? As far as I know, "close consumer" will not close a multiplexed connection. I am trying to understand what you have observed before. I guess "connection" here should not be used as the underlying TCP connection is kept open, rather "session". On reset, Pulsar will close every session. So, the problem is: 1. we have N (where N > 1) "read sessions" open 2. on initialization, the logic performs "seek" operation, so that it starts reading from the offset recorded externally 3. *every* session gets closed when *any* of the sessions performs the seek 4. [go back to 2.] This behaviour makes it impossible to store offsets outside of Pulsar due to the 2 -> 3 -> 2 loop
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
