[SERVER-66961] Don't check fastcount on FCBIS sharding tests Created: 02/Jun/22 Updated: 29/Oct/23 Resolved: 14/Jun/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Matthew Russotto | Assignee: | Adi Zaimi |
| 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: | 59 | ||||
| Description |
|
For any tests where we do FCBIS and sharding, the background writes to lockpings may cause a fastcount mismatch, which is a known issue with backup cursors and our size storer. I believe we can set TestData.skipEnforceFastCountOnValidate to not check fastcount in these tests. |
| Comments |
| Comment by Githook User [ 14/Jun/22 ] |
|
Author: {'name': 'Adi Zaimi', 'email': 'adizaimi@yahoo.com', 'username': 'adizaimi'}Message: |