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
Yes, RW does not commit back the offset back to pulsar broker. Can you share more about your use case and can message be managed by retention time, such as 7 days in kafka?
Yes, RW does not commit back the offset back to pulsar broker. Can you share more about your use case and can message be managed by retention time, such as 7 days in kafka?
Same issue, there are some trouble when rw does not send ack.
Monitor system is broken: pulsar-manager and dashboard will show all messages is backlog.
We have to set a larger retention policy to avoid message cleaned before consumed due to we don't know whether the messages is consumed correctly, It bring overload for disk space.
Describe the bug
it seems the pulsar source consume message but doesn't ack the message ,so the pulsar backlog size will increase day by day.
Error message/log
No response
To Reproduce
No response
Expected behavior
No response
How did you deploy RisingWave?
No response
The version of RisingWave
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: