[SERVER-37394] Invariant failure deadline != Date_t::max() or Invariant failure date.isFormattable() Created: 28/Sep/18 Updated: 29/Oct/23 Resolved: 09/Oct/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 4.0.2, 4.1.3 |
| Fix Version/s: | 4.0.4, 4.1.4 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Asya Kamsky | Assignee: | Eric Milkie |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Requested: |
v4.0
|
||||||||||||||||
| Sprint: | Storage NYC 2018-10-08 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 39 | ||||||||||||||||
| Description |
|
This happened in association with invariant seen in
In addition earlier in the logs there were a bunch of instances of this error:
|
| Comments |
| Comment by Githook User [ 11/Oct/18 ] |
|
Author: {'name': 'Eric Milkie', 'email': 'milkie@10gen.com', 'username': 'milkie'}Message: Because a lock acquisition can time out due to the minimum of the passed-in deadline or the MaxLockTimeout set on the Locker, we cannot show the exact deadline used for the timeout in the timeout message. (cherry picked from commit 1e03955cdab995fed6672d75a6a4544a9771a279) |
| Comment by Githook User [ 09/Oct/18 ] |
|
Author: {'name': 'Eric Milkie', 'email': 'milkie@10gen.com', 'username': 'milkie'}Message: Because a lock acquisition can time out due to the minimum of the passed-in deadline or the MaxLockTimeout set on the Locker, we cannot show the exact deadline used for the timeout in the timeout message. |