ROS2 Debug Log Filled up with Repeating Messages
I am working with a node that has a rate timer set at 5Hz and many subscribers to a bunch of sensors along with one approximate topic sync to a stereo camera pair. When I look at the debug logger level I am fed repeated messages resembling those that can be seen below at a very high rate. Any idea as to where they are generated and how to deal with them? They make it impossible to see the debug messages I care about that only show up once. The stream of messages does not seem to stop after even long periods of time. If it has any potential impact, I am using a ros1_bridge to get most of the topics and to send most of the messages to the rest of the robot. Thanks.
[DEBUG] [rcl]: Subscription take succeeded: true
[DEBUG] [rcl]: Subscription taking message
[DEBUG] [rcl]: Subscription take succeeded: true
[DEBUG] [rcl]: Waiting without timeout
[DEBUG] [rcl]: Timeout calculated based on next scheduled timer: false
[DEBUG] [rcl]: Guard condition in wait set is ready
[DEBUG] [rcl]: Waiting without timeout
[DEBUG] [rcl]: Timeout calculated based on next scheduled timer: false
[DEBUG] [rcl]: Subscription in wait set is ready
[DEBUG] [rcl]: Subscription taking message
[DEBUG] [rcl]: Waiting without timeout
[DEBUG] [rcl]: Subscription take succeeded: true
[DEBUG] [rcl]: Timeout calculated based on next scheduled timer: false
[DEBUG] [rcl]: Guard condition in wait set is ready
[DEBUG] [rcl]: Waiting without timeout
[DEBUG] [rcl]: Timeout calculated based on next scheduled timer: false
[DEBUG] [rcl]: Subscription in wait set is ready
[DEBUG] [rcl]: Subscription taking message
[DEBUG] [rcl]: Waiting without timeout
[DEBUG] [rcl]: Timeout calculated based on next scheduled timer: false
[DEBUG] [rcl]: Subscription take succeeded: true
[DEBUG] [rcl]: Guard condition in wait set is ready
[DEBUG] [rcl]: Waiting without timeout
[DEBUG] [rcl]: Timeout calculated based on next scheduled timer: false
[DEBUG] [rcl]: Subscription in wait set is ready
[DEBUG] [rcl]: Subscription in wait set is ready
[DEBUG] [rcl]: Subscription in wait set is ready
[DEBUG] [rcl]: Subscription taking message
[DEBUG] [rcl]: Subscription take succeeded: true
[DEBUG] [rcl]: Waiting without timeout
[DEBUG] [rcl]: Timeout calculated based on next scheduled timer: false
[DEBUG] [rcl]: Guard condition in wait set is ready
[DEBUG] [rcl]: Waiting without timeout
[DEBUG] [rcl]: Timeout calculated based on next scheduled timer: false
[DEBUG] [rcl]: Subscription in wait set is ready
[DEBUG] [rcl]: Subscription in wait set is ready
[DEBUG] [rcl]: Subscription in wait set is ready
[DEBUG] [rcl]: Subscription in wait set is ready
[DEBUG] [rcl]: Subscription in wait set is ready
[DEBUG] [rcl]: Subscription taking message
[DEBUG] [rcl]: Subscription take succeeded: true
[DEBUG] [rcl]: Waiting without timeout
[DEBUG] [rcl]: Timeout calculated based on next scheduled timer: false
[DEBUG] [rcl]: Guard condition in wait set is ready
[DEBUG] [rcl]: Waiting without timeout
[DEBUG] [rcl]: Timeout calculated based on next scheduled timer: false
[DEBUG] [rcl]: Subscription in wait set is ready
[DEBUG] [rcl]: Subscription in wait set is ready
[DEBUG] [rcl]: Subscription in wait set is ready
[DEBUG] [rcl]: Subscription in wait ...
Setting log level currently sets it for the entire node, including ROS' debug messages which you're seeing. It should be possible to filter in the next version of ROS. See this answer