v1.18: add metric for duplicate push messages (backport of #321) #505
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
We don't have any insight into what percentage of gossiped crds values are duplicates (or redundant)
Summary of Changes
Add a metric:
num_duplicate_push
that reports the number of duplicateCrdsValue
s received via push.num_total_push
that reports the total number ofCrdsValue
s received via push200 node test cluster on Monogon shows about 53% of Push messages are duplicates
This is an automatic backport of pull request #321 done by [Mergify](https://mergify.com).