[SERVER-53831] Force SpiderMonkey to garbage collect in ReplSetTest.checkOplogs Created: 15/Jan/21 Updated: 29/Oct/23 Resolved: 28/Jan/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0, 4.2.13, 4.4.5, 4.0.24 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Jason Chan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v4.4, v4.2, v4.0
|
||||||||
| Sprint: | Repl 2021-02-08 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 7 | ||||||||
| Description |
|
Certain tests, like the backup_restore_*.js tests, set a large oplog size. If the oplog becomes large (especially if there is a concentration of particularly large entries), SpiderMonkey can cause an OOM when checking the oplogs. This should be able to be fixed by manually having SpiderMonkey garbage collect (at least if the oplog is large), which is what the itcount function currently does to avoid this issue. |
| Comments |
| Comment by Githook User [ 17/Feb/21 ] |
|
Author: {'name': 'Jason Chan', 'email': 'jason.chan@mongodb.com', 'username': 'jasonjhchan'}Message: (cherry picked from commit 96fe72c36d370a4067240738f051021d4daf72ce) |
| Comment by Githook User [ 17/Feb/21 ] |
|
Author: {'name': 'Jason Chan', 'email': 'jason.chan@mongodb.com', 'username': 'jasonjhchan'}Message: (cherry picked from commit 96fe72c36d370a4067240738f051021d4daf72ce) |
| Comment by Githook User [ 17/Feb/21 ] |
|
Author: {'name': 'Jason Chan', 'email': 'jason.chan@mongodb.com', 'username': 'jasonjhchan'}Message: (cherry picked from commit 96fe72c36d370a4067240738f051021d4daf72ce) |
| Comment by Githook User [ 28/Jan/21 ] |
|
Author: {'name': 'Jason Chan', 'email': 'jason.chan@mongodb.com', 'username': 'jasonjhchan'}Message: |