[SERVER-29332] Call setFeatureCompatibilityVersion once instead of for each database Created: 08/May/17 Updated: 30/May/17 Resolved: 30/May/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Robert Guo (Inactive) | Assignee: | DO NOT USE - Backlog - Test Infrastructure Group (TIG) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
Setting the featureCompatibilityVersion to 3.4 requires updating a document and creating an index. Setting the featureCompatibilityVersion to 3.2 requires updating a document and dropping that index. The validate_collections.js hook sets the featureCompatibilityVersion to 3.4 for each collection when running the fuzzer. This causes additional I/O load on the machine and can lead to the test being considered as having timed out. We should instead change to set the featureCompatibilityVersion to 3.4 once while validating all collections on the server before setting it back to 3.2. |
| Comments |
| Comment by Max Hirschhorn [ 30/May/17 ] |
|
We'll just remove setting the featureCompatibilityVersion to 3.2 as part of |
| Comment by Max Hirschhorn [ 25/May/17 ] |
Thanks tess.avitabile, that sounds good to me. |
| Comment by Tess Avitabile (Inactive) [ 25/May/17 ] |
|
Yes, since |
| Comment by Max Hirschhorn [ 25/May/17 ] |
|
tess.avitabile, if |