-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set delivery_mode=2 (peristent) in v2 #1004
Labels
likely-fixed
likely fix is in the repository, success not confirmed yet.
Priority 4 - Strategic
would benefit multiple use cases if resolved
ReliabilityRecovery
improve behaviour in failure situations.
v2only
only affects v2 branches.
Comments
reidsunderland
added
v2only
only affects v2 branches.
Priority 4 - Strategic
would benefit multiple use cases if resolved
labels
Mar 28, 2024
With the change made, the v2 flakey_broker test passes, other than sarrac problems:
compared to v2_dev without the persistent delivery mode:
I'm guessing the sarrac problems are related to changes in sr_insects, not actual problems... |
petersilva
added
the
likely-fixed
likely fix is in the repository, success not confirmed yet.
label
Mar 29, 2024
fwiw... there is an sr_insects PR that updates the flow tests. |
petersilva
added
the
ReliabilityRecovery
improve behaviour in failure situations.
label
Apr 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
likely-fixed
likely fix is in the repository, success not confirmed yet.
Priority 4 - Strategic
would benefit multiple use cases if resolved
ReliabilityRecovery
improve behaviour in failure situations.
v2only
only affects v2 branches.
We recently discovered that v2 does not publish peristent messages:
sarracenia/sarra/sr_amqp.py
Lines 388 to 416 in 5b063af
(delivery_mode is either not set, or set to 1, which is transient).
This means that messages are lost when a broker is restarted.
In sr3, we use delivery_mode=2, persistent.
sarracenia/sarracenia/moth/amqp.py
Lines 719 to 723 in 07b38e6
The text was updated successfully, but these errors were encountered: