[SERVER-28459] Simulate the Max Int reached into the LogicalClock error Created: 23/Mar/17 Updated: 06/Dec/17 Resolved: 16/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.9 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Misha Tyulenev | Assignee: | Jack Mulrow |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2017-06-19, Sharding 2017-07-10 |
| Participants: |
| Description |
|
Add fassert to LogicalTime::reserveTicks that checks if its try to set the max time. |
| Comments |
| Comment by Githook User [ 16/Jun/17 ] |
|
Author: {u'username': u'jsmulrow', u'name': u'Jack Mulrow', u'email': u'jack.mulrow@mongodb.com'}Message: |