[SERVER-54834] Read write concern defaults propagation jstests should not assert on wall clock times Created: 26/Feb/21 Updated: 29/Oct/23 Resolved: 03/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Sergi Mateo Bellido |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 26 | ||||
| Description |
|
The read_write_concern_defaults_propagation.js jstestsĀ assert the wall clock time when a node caches read write concern defaults is always >= the wall clock time when the defaults were generated. These wall clock times come from separate calls to the system clock, which is not guaranteed to be monotonic, so this assert can fail if the clock jumps backward between the calls. The test should either not assert on the wall clock times or make the assertion less strict. |
| Comments |
| Comment by Githook User [ 03/May/21 ] |
|
Author: {'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}Message: Even if all host run on the same machine, we cannot compare wall clock |