[SERVER-38246] profiled oplog getMore command can be confusing Created: 26/Nov/18 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.4.18, 4.0.4 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Zhang Youdong | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | qexec-team | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Execution
|
| Participants: |
| Description |
|
There are a lot of slow log in local database because of fetching oplog timeout., and the execStats output is very confused for users.
|
| Comments |
| Comment by Zhang Youdong [ 28/Nov/18 ] |
|
It's an internal design that fetching oplog timeout in 5s(default), the users shouldn't care about this issues, users may think it's a real slow query. |
| Comment by Danny Hatcher (Inactive) [ 26/Nov/18 ] |
|
Hello, Many users find messages such as these useful in troubleshooting slow performance for individual MongoDB nodes. Is there a specific concern that you have with the messages? Thank you, Danny |