Skip to content
This repository has been archived by the owner on Jun 19, 2022. It is now read-only.

Determine default target for broker retry delivery attempts per second #1598

Closed
grantr opened this issue Aug 18, 2020 · 2 comments
Closed

Determine default target for broker retry delivery attempts per second #1598

grantr opened this issue Aug 18, 2020 · 2 comments
Assignees
Labels
area/broker kind/feature-request New feature or request priority/1 Blocks current release defined by release/* label or blocks current milestone release/2 storypoint/2
Milestone

Comments

@grantr
Copy link
Contributor

grantr commented Aug 18, 2020

Problem
What is our default target for delivery attempts per second handled by the broker retry service?

This could be defined as a percentage of delivery attempt rate (#1597), for example "10% of delivery attempts will be retried," but since events may be retried multiple times, it's probably clearer to set an explicit rate goal.

Persona:
User

Exit Criteria
We have a goal in delivery attempts per second to tune the default fanout resource requirements.

Additional context (optional)
Part of #1552.

@grantr grantr added kind/feature-request New feature or request area/broker priority/1 Blocks current release defined by release/* label or blocks current milestone release/2 labels Aug 18, 2020
@grantr grantr added this to the Backlog milestone Aug 25, 2020
@grantr grantr modified the milestones: Backlog, v0.18.0-M2 Sep 2, 2020
@cathyzhyi cathyzhyi self-assigned this Sep 3, 2020
@grantr grantr modified the milestones: v0.18.0-M2, Backlog Sep 9, 2020
@grantr grantr modified the milestones: Backlog, v0.18.0-M3 Sep 16, 2020
@grantr grantr modified the milestones: v0.18.0-M3, v0.19.0-M1 Sep 30, 2020
@grantr
Copy link
Contributor Author

grantr commented Oct 6, 2020

Decided on 10% of total throughput being retried.

@cathyzhyi
Copy link
Contributor

cathyzhyi commented Oct 6, 2020

The default target for retry is set to cover 10% failure rate for the fanout delivery. The resulting throughput is sum of a geometric progression with scale factor of 10% and base of 2.5Gb which is fanout target throughput set in #1597 . ( 10%+10%*10% + 10%*10%*10%....)*2.5 Gb/s ~280Mb/s. The target throughput is multiplying payload size * qps * number of triggers so there are scenarios with different combinations from the 3 dimensions when considering the resource request.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/broker kind/feature-request New feature or request priority/1 Blocks current release defined by release/* label or blocks current milestone release/2 storypoint/2
Projects
None yet
Development

No branches or pull requests

2 participants