[SERVER-40955] Blacklist agg_sort.js in concurrency_replication_for_backup_restore suite Created: 02/May/19 Updated: 29/Oct/23 Resolved: 06/May/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework, Querying |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.11 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Anton Korshunov | Assignee: | Anton Korshunov |
| 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 | ||||
| Participants: | |||||
| Linked BF Score: | 7 | ||||
| Description |
|
Aggregation sort workloads use large volumes of data and can overwhelm test hosts causing OOM killer to kick in while running backup/restore test suits. |
| Comments |
| Comment by Githook User [ 06/May/19 ] |
|
Author: {'email': 'anton.korshunov@mongodb.com', 'name': 'Anton Korshunov', 'username': 'antkorsh'}Message: |
| Comment by Anton Korshunov [ 03/May/19 ] |
|
We already have agg_sort_external.js blacklisted, which differs from agg_sort.js in that it can spill data on disk if it doesn't feet into 100mb limit. I also compared memory footprint of various workloads which use agg_sort and it's not any different from what is seen in case of backup/restore, so this test is not friendly to the backup/restore workload and should be blacklisted. |