[SERVER-46862] Log shutdown timestamps in Timestamp format Created: 13/Mar/20 Updated: 29/Oct/23 Resolved: 24/Mar/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Daniel Gottlieb (Inactive) | Assignee: | Daniel Gottlieb (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Execution Team 2020-04-06 | ||||
| Participants: | |||||
| Description |
|
Originally, WT logged timestamps in their 64-bit form, thus it made sense for the pieces interfacing with WT to also log values the same way. However, now WT logs timestamps in their high-32/low-32 bit (timestamp) representation. It would be useful to convert these values to match. Additionally, due to a lobster JSON parsing bug, the 64-bit values lose precision in a way that makes diagnosing problems harder. |
| Comments |
| Comment by Githook User [ 24/Mar/20 ] |
|
Author: {'name': 'Daniel Gottlieb', 'username': 'dgottlieb', 'email': 'daniel.gottlieb@mongodb.com'}Message: |