Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Extend wait-before-drop config options for multi-fragment messages #1539

Closed
yellowhatter opened this issue Oct 16, 2024 · 2 comments
Closed

Extend wait-before-drop config options for multi-fragment messages #1539

yellowhatter opened this issue Oct 16, 2024 · 2 comments
Assignees
@yellowhatter
Labels
new feature Something new is needed

Comments

@yellowhatter
Copy link
Contributor

yellowhatter commented Oct 16, 2024 •
edited
Loading

Describe the feature

After #1510 and discussion we decided that we need to configure deadline adoption function to be:

  • non-linear
  • limited with some upper boundary
@yellowhatter yellowhatter added the new feature Something new is needed label Oct 16, 2024
@yellowhatter yellowhatter self-assigned this Oct 16, 2024
@yellowhatter
Copy link
Contributor Author

The proposition was to calculate deadline as:
deadline = prev_deadline * 2
with limitation to some config-defined upper boundary value

@Mallets
Copy link
Member

Mallets commented Nov 28, 2024

Closed by #1603

@Mallets Mallets closed this as completed Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@yellowhatter yellowhatter

Labels
new feature Something new is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Mallets @yellowhatter