WIP: Improve federation backoff logic #1182
No reviewers
Labels
No labels
Bug
Cherry-picking
Database
Dependencies
Dependencies/Renovate
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/Federation
Matrix/Hydra
Matrix/MSC
Matrix/Media
Meta
Meta/CI
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status/Blocked
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Support
To-Merge
Wont fix
old/ci/cd
old/rust
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
continuwuation/continuwuity!1182
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "nex/fix/backoff"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR will fix up some of the federation sender code to fix the issue where servers get banished to backoff purgatory for an undefined amount of time which may also be different depending on which sender worker fails.
This will not fix issues like lookup errors poisoning the destinations cache, that is a separate issue.
Things to do:
@ -556,4 +556,1 @@[workspace.dependencies.resolv-conf]version = "0.7.5"where'd resolv-conf go wtf
@ -101,6 +103,7 @@ impl crate::Service for Service {federation: args.depend::<federation::Service>("federation"),},channels: (0..num_senders).map(|_| loole::unbounded()).collect(),statuses: vec![sender::CurTransactionStatus::new(); num_senders],This is still splitting into multiple statuses different per worker?
Yes, we need that for concurrent sending. The status registry tracks the state of a destination per-worker, if one is actively sending and the registry is global, then all other workers will refuse to send until that one completes
97c13d8c77ae595dd0d1View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.