mirror of
https://github.com/lightningdevkit/rust-lightning.git
synced 2025-03-15 15:39:09 +01:00
Add logging around event processing.
Currently we don't have any visibility if BackgroundProcessor takes considerably more of time to process events, adding logs to help debug such issues.
This commit is contained in:
parent
a75fdaba3b
commit
85eb8145fb
1 changed files with 10 additions and 0 deletions
|
@ -325,9 +325,17 @@ macro_rules! define_run_body {
|
|||
let mut have_decayed_scorer = false;
|
||||
|
||||
loop {
|
||||
log_trace!($logger, "Processing ChannelManager events...");
|
||||
$process_channel_manager_events;
|
||||
log_trace!($logger, "Done processing ChannelManager events.");
|
||||
|
||||
log_trace!($logger, "Processing ChainMonitor events...");
|
||||
$process_chain_monitor_events;
|
||||
log_trace!($logger, "Done processing ChainMonitor events.");
|
||||
|
||||
log_trace!($logger, "Processing OnionMessageHandler events...");
|
||||
$process_onion_message_handler_events;
|
||||
log_trace!($logger, "Done processing OnionMessageHandler events.");
|
||||
|
||||
// Note that the PeerManager::process_events may block on ChannelManager's locks,
|
||||
// hence it comes last here. When the ChannelManager finishes whatever it's doing,
|
||||
|
@ -340,7 +348,9 @@ macro_rules! define_run_body {
|
|||
// ChannelManager, we want to minimize methods blocking on a ChannelManager
|
||||
// generally, and as a fallback place such blocking only immediately before
|
||||
// persistence.
|
||||
log_trace!($logger, "Processing PeerManager events...");
|
||||
$peer_manager.as_ref().process_events();
|
||||
log_trace!($logger, "Done processing PeerManager events.");
|
||||
|
||||
// Exit the loop if the background processor was requested to stop.
|
||||
if $loop_exit_check {
|
||||
|
|
Loading…
Add table
Reference in a new issue