[SERVER-7440] Better logging when timeout is exceeded with getLastError Created: 22/Oct/12 Updated: 06/Dec/22 Resolved: 08/Dec/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andre de Frere | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Query
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Participants: | |||||
| Description |
|
Currently when an operation exceeds the getLastError timeout value, we would see a message similar to the following:
Which is easily missed, and does not mention the actual problem - that the time out has been exceeded. A better log message indicating the that timeout had been exceeded would be more useful. |
| Comments |
| Comment by Asya Kamsky [ 08/Dec/17 ] |
|
Since getLastError is only used with legacy writes, we won't be changing its logging. |