[SERVER-46080] Document sigusr2 Created: 11/Feb/20  Updated: 29/Oct/23  Resolved: 21/Feb/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.3.4

Type: Task Priority: Major - P3
Reporter: Sara Williamson Assignee: Billy Donahue
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
is documented by DOCS-13441 Investigate changes in SERVER-46080: ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Dev Tools 2020-02-24
Participants:

 Description   

We should add some text similar to the following to the manual, where troubleshooters will see it as a tool in the toolbox:

"On Linux (currently supported only for x86-64 architectures), we have introduced a runtime diagnostic feature in v4.3.4+. When a mongod or mongos process receives a SIGUSR2 signal, it will log a backtrace for each of its threads. Such log lines can be piped into buildscripts/mongosymb.py for expansion into more precise code locations."



 Comments   
Comment by Billy Donahue [ 21/Feb/20 ]

We should add some text similar to the following to the manual, where troubleshooters will see it as a tool in the toolbox:

"On Linux (currently supported only for x86-64 architectures), we have introduced a runtime diagnostic feature in v4.3.4+. When a mongod or mongos process receives a SIGUSR2 signal, it will log a backtrace for each of its threads. Such log lines can be piped into buildscripts/mongosymb.py for expansion into more precise code locations."

Generated at Thu Feb 08 05:10:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.