-
Notifications
You must be signed in to change notification settings - Fork 47
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
fix: tracer to track delivered message if duplicate #385
Conversation
Codecov ReportBase: 83.26% // Head: 83.22% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #385 +/- ##
==========================================
- Coverage 83.26% 83.22% -0.04%
==========================================
Files 48 48
Lines 11787 11797 +10
Branches 1266 1266
==========================================
+ Hits 9814 9818 +4
- Misses 1973 1979 +6
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add metrics to verify this hypothesis?
- Add a second parameter to
deliverMessage(msg, isDuplicate: boolean)
- In that function, if promise resolved and isDuplicate then
this.metrics.iwantPromiseResolvedFromDuplicate.inc(1)
a249d0e
to
55cdaad
Compare
thanks @dapplion for the metric, it shows a lot of promises could be resolved by duplicate messages (this is from a mainnet node subscribing to all subnets) it could reduce 80% 90% of broken promises (this was only tested 3h but we could trust as these 2 metrics match each other) |
Motivation
Description
tracer. deliverMessage()
in the case of message duplicatepart of ChainSafe/lodestar#4818