-
Notifications
You must be signed in to change notification settings - Fork 493
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
node: Add logging thread to node monitoring wg #4934
Conversation
Codecov Report
@@ Coverage Diff @@
## master #4934 +/- ##
==========================================
+ Coverage 53.51% 53.53% +0.02%
==========================================
Files 432 432
Lines 53615 53616 +1
==========================================
+ Hits 28691 28706 +15
+ Misses 22695 22682 -13
+ Partials 2229 2228 -1
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
@@ -399,6 +399,7 @@ func (node *AlgorandFullNode) startMonitoringRoutines() { | |||
go node.oldKeyDeletionThread(node.ctx.Done()) | |||
|
|||
if node.config.EnableUsageLog { | |||
node.monitoringRoutinesWaitGroup.Add(1) |
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.
there is not corresponding monitoringRoutinesWaitGroup.Done()
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.
Ah you're right. It should be passed in via go logging.UsageLogThread(node.ctx, node.log, 100*time.Millisecond, node.monitoringRoutinesWaitGroup)
. I'm curious why we ended up passing nil instead.
Summary
This commit runs a goroutine without adding it to the monitoring wg.