Closed ptoews closed 3 months ago
I tried to additionally clear the subscribers first, but that didn't help. Then, I got it working by simply closing the consumer instead of just unsubscribing. However, I don't think this is a good solution, as it has to initiate a new connection.
I had a look at what close() does, and it seems it's just these three steps:
but since manually doing just 1 and 2 didn't work, it seems to require closing the connection, which doesn't make sense to me. Surely I am missing something?
Hey Hi @ptoews thanks to have reported this. I will have a look even if it may take a while!
@ptoews it seems like the issue is when we subscribe again with the same subscriber_name, I need to investigate why this is happening. Can you try to subscribe in seek_somewhere with a different APP_ID?
@DanielePalaia Yes, that did work, thank you!
@ptoews Great! I'll leave this issue open (changing the title) as there is probably a bug in the code
HI @ptoews I implemented a fix in this PR https://github.com/qweeze/rstream/pull/199 that should allow you to use the same subscriber_name. I made a few tests and it seems working fine. Maybe you can also do a few tests on your previous scenario?
@DanielePalaia Awesome, I did some quick initial tests and didn't find any issues so far.
Hi,
we would like to seek to a different timestamp while a subscription is already running. I tried to simplify our current approach to this script:
However, this doesn't work. Messages are received, until the seeking is attempted, after which no more messages are received (but the program keeps running).
What is the best way to do this? Do we have to create a new consumer?
Thanks for any help in advance.