[SERVER-20231] update config.mongos take too long to run 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 |
|
I'm seeing lots of these in the sharded cluster logs: update: { $set: { ping: new Date(1441032748030), up: 2830090, waiting: false, mongoVersion: "3.0.5" }} nscanned:1 nscannedObjects:1 nMatched:1 nModified:1 fastmod:1 keyUpdates:0 writeConflicts:0 numYields:0 locks:{ Global: { acquireCount: { r: 2, w: 2 }}, MMAPV1Journal: { acquireCount: { w: 2 }, acquireWaitCount: { w: 1 }, timeAcquiringMicros: { w: 117320 }}, Database: { acquireCount: { w: 2 }}, Collection: { acquireCount: { W: 2 }} } 117ms 2015-08-31T06:14:50.942-0700 I WRITE [conn21436] update config.mongos query: { _id: "profile-001b.staging.dccl:27017" }update: { $set: { ping: new Date(1441026890836), up: 2823899, waiting: false, mongoVersion: "3.0.5" }} nscanned:1 nscannedObjects:1 nMatched:1 nModified:1 fastmod:1 keyUpdates:0 writeConflicts:0 numYields:0 locks:{ Global: { acquireCount: { r: 2, w: 2 }}, MMAPV1Journal: { acquireCount: { w: 2 }, acquireWaitCount: { w: 1 }, timeAcquiringMicros: { w: 104858 }}, Database: { acquireCount: { w: 2 }}, Collection: { acquireCount: { W: 2 }} } 105ms 2015-08-30T22:46:05.694-0700 I WRITE [conn41724] update config.mongos query: { _id: "transaction-002b.prod.dccl:27017" }update: { $set: { ping: new Date(1440999965536), up: 372470, waiting: false, mongoVersion: "3.0.6" }} nscanned:1 nscannedObjects:1 nMatched:1 nModified:1 fastmod:1 keyUpdates:0 writeConflicts:0 numYields:0 locks:{ Global: { acquireCount: { r: 2, w: 2 }}, MMAPV1Journal: { acquireCount: { w: 2 }, acquireWaitCount: { w: 1 }, timeAcquiringMicros: { w: 154476 }}, Database: { acquireCount: { w: 2 }}, Collection: { acquireCount: { W: 2 }} } 154ms 2015-08-30T22:37:33.179-0700 I WRITE [conn7] update config.mongos query: { _id: "etl-001b.prod.dccl:27017" }update: { $set: { ping: new Date(1440999453060), up: 7013430, waiting: false, mongoVersion: "3.0.2" }} nscanned:1 nscannedObjects:1 nMatched:1 nModified:1 fastmod:1 keyUpdates:0 writeConflicts:0 numYields:0 locks:{ Global: { acquireCount: { r: 2, w: 2 }}, MMAPV1Journal: { acquireCount: { w: 2 }, acquireWaitCount: { w: 1 }, timeAcquiringMicros: { w: 116568 }}, Database: { acquireCount: { w: 2 }}, Collection: { acquireCount: { W: 2 } } } 116ms |
| 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. |