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
Describe the bug
A clear and concise description of what the bug is.
We have been using eventstoredb for months now and have a considerable amount of events. We mistakenly ran parked messages from the console ( could be improved at least a warning before it runs). We had so many messages around 380k messages sent the subscription that was a lot of messages but the parked messages was no were near this number and checking the data in those events they appear to be for streams but they are deleted events. Question here
Does replaying parked messages play deleted messages, or parked messages are indefinitely in the stream even if they don't appear in the console?
To Reproduce
Steps to reproduce the behavior:
1.
2.
3.
4.
Expected behavior
Just a few parked events to replayed
Actual behavior
Almost 380k too many events were send through the subscription
Config/Logs/Screenshots
If applicable, please attach your node configuration, logs or any screenshots.
EventStore details
EventStore server version:
Operating system:
EventStore client version (if applicable):
Additional context
Add any other context about the problem here.
Describe the bug
A clear and concise description of what the bug is.
We have been using eventstoredb for months now and have a considerable amount of events. We mistakenly ran parked messages from the console ( could be improved at least a warning before it runs). We had so many messages around 380k messages sent the subscription that was a lot of messages but the parked messages was no were near this number and checking the data in those events they appear to be for streams but they are deleted events. Question here
Does replaying parked messages play deleted messages, or parked messages are indefinitely in the stream even if they don't appear in the console?
To Reproduce
Steps to reproduce the behavior:
1.
2.
3.
4.
Expected behavior
Just a few parked events to replayed
Actual behavior
Almost 380k too many events were send through the subscription
Config/Logs/Screenshots
If applicable, please attach your node configuration, logs or any screenshots.
EventStore details
Additional context
Add any other context about the problem here.
DB-332
The text was updated successfully, but these errors were encountered: