[SERVER-42131] Modify test to account for storage engines that do not support the replSetResizeOplog command Created: 09/Jul/19 Updated: 27/Oct/23 Resolved: 12/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Vishnu Kaushik | Assignee: | Backlog - Replication Team |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 47 | ||||||||||||||||||||
| Description |
|
The issue: Not all storage engines support the replSetResizeOplog command (see
Proposed fixes: A solution is to remove the line that tries to maintain uniformity at the start of each test. Since this is a part of the auth suite, it is unlikely that the particular size of the oplog even matters. Another solution is to introduce the isWiredTigerOrInMemory() check - only when it is true, then issue the replSetResizeOplog command. Otherwise, just drop and create a new oplog. I think this is the best solution. |
| Comments |
| Comment by Vishnu Kaushik [ 12/Jul/19 ] |
|
jason.chan Yes, I think we could merge them together. |
| Comment by Jason Chan [ 11/Jul/19 ] |
|
vishnu.kaushik Does it make sense to merge this ticket with |