[SERVER-35826] Log UUID when ValidateCollections detects a UUID in SchemaVersion 3.4 Created: 26/Jun/18 Updated: 06/Dec/22 Resolved: 19/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Catalog, Testing Infrastructure, Upgrade/Downgrade |
| Affects Version/s: | 3.6.5 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Maria van Keulen | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | stm | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
In MongoDB 3.6 collection validation, we check that UUIDs are present when featureCompatibilityVersion is 3.6 and not present when featureCompatibilityVersion is 3.4. If a UUID is erroneously present when FCV is 3.4, we should log what the UUID is to more easily trace the offending collection in the logs. |
| Comments |
| Comment by Maria van Keulen [ 15/Jul/18 ] |
|
max.hirschhorn I believe it would be convenient to also have logs of the UUID as part of the ValidateCollections UUID check. It would save the extra step of finding the UUID corresponding to the collection at the time of the ValidateCollections check in the dbHash logs. |
| Comment by Max Hirschhorn [ 02/Jul/18 ] |
|
maria.vankeulen, are you wanting the server to include the UUID of the collection in its response (we recently did this for the dbHash command as part of |