[SERVER-59066] About mongotop and {"top":1} unexpected returns Created: 29/Jul/21 Updated: 06/Dec/22 Resolved: 12/Aug/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Trivial - P5 |
| Reporter: | 皓琛 崔 | Assignee: | Backlog - Triage Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
3.2.10 |
||
| Attachments: |
|
| Assigned Teams: |
Server Triage
|
| Participants: |
| Description |
|
recently took over an old cluster's maintaince returns removed collection data and unexpected data (see pics) |
| Comments |
| Comment by Edwin Zhou [ 12/Aug/21 ] |
|
Thanks for your report. Please note that the SERVER project is for bugs for the MongoDB server. As this ticket does not appear to be a bug, I will now close it. If you need further assistance troubleshooting, I encourage you to ask our community by posting on the MongoDB Developer Community Forums. Best, |
| Comment by Ryan Chipman [ 03/Aug/21 ] |
|
Hi qq289513270@gmail.com, I'm moving this ticket to the SERVER project, because your question re: how to reset the top command data is a question about MongoDB Server itself, not one specific to the Database Tools – mongotop simply displays the data it receives from the top command. |