[SERVER-31614] log when we assign or remove a collection's UUID in tests Created: 18/Oct/17 Updated: 30/Oct/23 Resolved: 03/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.0-rc3 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Xiangyu Yao (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Storage 2017-11-13 |
| Participants: |
| Description |
|
To better investigate UUID related BFs, we've been trying to log the entire lifecycle of each collection. An important part of that is when collections are assigned UUIDs. Since this action does not happen often, it seems reasonable. |
| Comments |
| Comment by Githook User [ 03/Nov/17 ] |
|
Author: {'name': 'Xiangyu Yao', 'username': 'xy24', 'email': 'xiangyu.yao@mongodb.com'}Message: |