You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An event which delivered to sink failed will be put to timing queue. when the timing event comes to the time, it will be put to retry eventbus. The trigger will read event from retry eventbus and then attempt to deliver the event to sink again. But when the subscription reset offset, how to deal with retry eventbus? vanus will reset the retry eventbus offset to the latest, but the events which are in the timing queue have not been clean, then it will be put to retry eventbus too, now it fits "at least once" semantics. How to handle retry events in the future?
The text was updated successfully, but these errors were encountered:
when the subscription reset offset, vanus will reset the retry eventbus offset to the latest, but if the events in the timing queue have not been clean, then it will be put to retry eventbus too, now it fits "at least once" semantics.
If the timer supports delete, we then decide whether to delete the event which in timer queue
An event which delivered to sink failed will be put to timing queue. when the timing event comes to the time, it will be put to retry eventbus. The trigger will read event from retry eventbus and then attempt to deliver the event to sink again. But when the subscription reset offset, how to deal with retry eventbus? vanus will reset the retry eventbus offset to the latest, but the events which are in the timing queue have not been clean, then it will be put to retry eventbus too, now it fits "at least once" semantics. How to handle retry events in the future?
The text was updated successfully, but these errors were encountered: