[SERVER-14273] Record current operations before shutdown/assertions Created: 16/Jun/14  Updated: 08/Mar/16  Resolved: 07/Mar/16

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

Type: Improvement Priority: Minor - P4
Reporter: Charlie Page Assignee: DO NOT USE - Backlog - Platform Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Participants:

 Description   

It would be helpful to record all of the current operations during shutdown. This would be especially helpful in the case of a fatal assertion, or when diagnosing slow operations if the server is shutdown manually.

This would also be useful during transitions within a replica member (like primary->secondary, of secondary->recovery).



 Comments   
Comment by Mira Carey [ 07/Mar/16 ]

Resolving as wont fix because we solved the problem differently in ftdc

Comment by Charlie Page [ 17/Jun/14 ]

This keeps the original intent. I'm thinking the best way is probably to print it out just like "normal" but with perhaps some identifier like "shutdown" so that mtools can easily integrate with it and reason for the query being ended is clear. currentOp() would introduce an additional format for automated tools.

Comment by Thomas Rueckstiess [ 17/Jun/14 ]

Hey charlie.page@10gen.com,

Scott rephrased the description of the ticket a little. Does this still reflect what you originally intended with this ticket?

How do you think the information should be accessible? Do you suggest to dump the db.currentOp() output to the log file on shutdown?

Thomas

Generated at Thu Feb 08 03:34:20 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.