[SERVER-18829] Cache usage exceeds configured maximum during index builds under WiredTiger Created: 04/Jun/15 Updated: 30/Mar/16 Resolved: 26/Jun/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.0.3 |
| Fix Version/s: | 3.0.5, 3.1.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Bruce Lucas (Inactive) | Assignee: | Michael Cahill (Inactive) |
| Resolution: | Done | Votes: | 4 |
| Labels: | RF, WTmem, WTplaybook | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||||||||||||||||||
| Backport Completed: | |||||||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Issue Status as of Jul 14, 2015 ISSUE SUMMARY This issue may prevent large index builds in some situations, such as during initial sync of new replica set members. USER IMPACT WORKAROUNDS AFFECTED VERSIONS FIX VERSION Original descriptionThis has been seen under somewhat different circumstances by a couple of customers. Initial sync of a large db (multi TB, couple billion documents). Foreground build of _id index starts at A, and cache usage rises steadily to 6x configured maximum before being terminated by OOM.
Mongorestore of 100GB db. Multiple parallel background index builds begin at A; at B cache usage begins to grow until it reaches about 1.5x configured max and is terminated by OOM.
No complete repro yet, although may have got a partial repro: during initial sync of a 500 GB db cache usage briefly rose to about 120% of configured max. |
| Comments |
| Comment by Githook User [ 29/Jun/15 ] |
|
Author: {u'username': u'agorrod', u'name': u'Alex Gorrod', u'email': u'alexander.gorrod@mongodb.com'}Message: (cherry picked from commit d57dc26729bbc59c5bc3928aa90bb2ac3cd15d6d) |
| Comment by Alexander Gorrod [ 10/Jun/15 ] |
|
A fix for this is now in MongoDB master, and will be included in the 3.1.5 release. |
| Comment by Githook User [ 10/Jun/15 ] |
|
Author: {u'username': u'agorrod', u'name': u'Alex Gorrod', u'email': u'alexander.gorrod@mongodb.com'}Message: Merge pull request #2018 from wiredtiger/read-gen-midpoint
|
| Comment by Githook User [ 10/Jun/15 ] |
|
Author: {u'username': u'michaelcahill', u'name': u'Michael Cahill', u'email': u'michael.cahill@mongodb.com'}Message: |
| Comment by Githook User [ 10/Jun/15 ] |
|
Author: {u'username': u'agorrod', u'name': u'Alex Gorrod', u'email': u'alexander.gorrod@mongodb.com'}Message: Merge pull request #2018 from wiredtiger/read-gen-midpoint
|
| Comment by Githook User [ 10/Jun/15 ] |
|
Author: {u'username': u'michaelcahill', u'name': u'Michael Cahill', u'email': u'michael.cahill@mongodb.com'}Message: |
| Comment by Githook User [ 10/Jun/15 ] |
|
Author: {u'username': u'agorrod', u'name': u'Alex Gorrod', u'email': u'alexander.gorrod@mongodb.com'}Message: Merge pull request #2018 from wiredtiger/read-gen-midpoint
|
| Comment by Githook User [ 10/Jun/15 ] |
|
Author: {u'username': u'michaelcahill', u'name': u'Michael Cahill', u'email': u'michael.cahill@mongodb.com'}Message: |