[DOCS-6280] Document saveState and restoreState fields in explain.executionStats Created: 27/Sep/15 Updated: 30/Oct/23 Resolved: 09/Oct/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | mongodb-3.0 |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Stennie Steneker (Inactive) | Assignee: | Nicholas Larew |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 5 years, 4 weeks ago | ||||
| Description |
|
The `saveState` and `restoreState` fields in MongoDB 3.0 explain.executionStats are not currently documented: These are counters for the number of times a query stage yielded (saveState) and then resumed (restoreState). For example, a collection scan (COLLSCAN) stage might need to yield to fetch documents that aren't in memory yet. Queries also yield so they can be interleaved with other queries and safely stopped via $maxTimeMS or kill operations. Ref: https://github.com/mongodb/mongo/blob/v3.0/src/mongo/db/query/explain.cpp#L223 |
| Comments |
| Comment by Githook User [ 16/Jan/19 ] |
|
Author: {'username': 'nlarew', 'email': 'nick.larew@10gen.com', 'name': 'Nick Larew'}Message: |
| Comment by Githook User [ 04/Dec/17 ] |
|
Author: {'username': 'nlarew', 'email': 'nick.larew@10gen.com', 'name': 'Nick Larew'}Message: |
| Comment by Kay Kim (Inactive) [ 30/May/17 ] |
|
Notes:
|