problem of ReceiveAsync

Question

problem of ReceiveAsync

Closed this issue 5 years ago · 2 comments

In ReceiveAsync, the ideal situation is that each time the client calls flow(n), after receiving the nth message, it executes flow(n). But in actual situations, the number of messages returned by the pulsar service is sometimes less than n. This will cause the next flow to never be triggered, and then the message will be stacked.

LvBay commented 5 years ago

loop flow

Answer 1 · 2019-09-10T09:59:03.000Z

In order to solve this problem, we can use time.Ticker to set a special timed task, and call flow(n) every once in a while. However, there will be a lot of tickers that will not be recycled in this program, which will put some pressure on the CPU. Maybe we have a better way?