[SERVER-20230] IXSCAN on sharded cluster Created: 31/Aug/15 Updated: 31/Aug/15 Resolved: 31/Aug/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Van Pham | Assignee: | Andre de Frere |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
We see lots of these IXSCAN on our sharded cluster when we do load test: planSummary: IXSCAN { id: "hashed" }ntoskip:0 nscanned:1 nscannedObjects:1 keyUpdates:0 writeConflicts:0 numYields:1 nreturned:1 reslen:67823 locks:{ Global: { acquireCount: { r: 4 }}, MMAPV1Journal: { acquireCount: { r: 2 }}, Database: { acquireCount: { r: 2 }}, Collection: { acquireCount: { R: 2 } } } 174ms planSummary: IXSCAN { id: "hashed" }ntoskip:0 nscanned:1 nscannedObjects:1 keyUpdates:0 writeConflicts:0 numYields:1 nreturned:1 reslen:67823 locks:{ Global: { acquireCount: { r: 4 }}, MMAPV1Journal: { acquireCount: { r: 2 }}, Database: { acquireCount: { r: 2 }}, Collection: { acquireCount: { R: 2 }} } 184ms 2015-08-27T16:38:19.294-0700 I QUERY [conn175973] query DCU.UserData query: { id: "UserData:ed360e776993d42b80ab8d91" }planSummary: IXSCAN { id: "hashed" }ntoskip:0 nscanned:1 nscannedObjects:1 keyUpdates:0 writeConflicts:0 numYields:1 nreturned:1 reslen:67824 locks:{ Global: { acquireCount: { r: 4 }}, MMAPV1Journal: { acquireCount: { r: 2 }}, Database: { acquireCount: { r: 2 }}, Collection: { acquireCount: { R: 2 }} } 182ms |
| Comments |
| Comment by Andre de Frere [ 31/Aug/15 ] |
|
Thanks for your report. Please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. A question like this involving more discussion would be best posted on the mongodb-user group. See also our Technical Support page for additional support resources. |