[SERVER-38294] WiredTiger oplog manager should include pretty-printed visibility timestamp in log message Created: 28/Nov/18 Updated: 29/Oct/23 Resolved: 06/Dec/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.7 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | William Schultz (Inactive) | 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 NYC 2018-12-17 |
| Participants: |
| Description |
|
WiredTigerOplogManager::_setOplogReadTimestamp prints out the new oplog visibility read timestamp as a raw uint64_t. For logging purposes it would probably be more useful to include the structured Timestamp e.g.
instead of
|
| Comments |
| Comment by Githook User [ 06/Dec/18 ] |
|
Author: {'name': 'Xiangyu Yao', 'email': 'xiangyu.yao@mongodb.com', 'username': 'xy24'}Message: |