[SERVER-55371] 4.2.13 removed rs.initiate() return object time values Created: 19/Mar/21 Updated: 27/Oct/23 Resolved: 04/Aug/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.2.13 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Anna Henningsen | Assignee: | Jack Mulrow |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Sprint: | Sharding 2021-04-05, Sharding 2021-04-19, Sharding 2021-05-03 | ||||||||||||
| Participants: | |||||||||||||
| Description |
| Comments |
| Comment by Jack Mulrow [ 04/Aug/21 ] |
|
Cluster time metadata is only returned when cluster time signing keys are available, which isn't guaranteed immediately after initiating a replica set. This has been the behavior since causal consistency was introduced, the change in |
| Comment by Daniel Gottlieb (Inactive) [ 23/Mar/21 ] |
|
Thanks for that information jack.mulrow! I'll see further vet my claim and see if it makes sense doing that. |
| Comment by Jack Mulrow [ 23/Mar/21 ] |
|
The problem So all that is to say I do think your idea is reasonable, so long as after executing replSetInitiate the node is guaranteed to be in a readable state. |
| Comment by Daniel Gottlieb (Inactive) [ 22/Mar/21 ] |
|
Thanks jack.mulrow. I believe the command causes mongod to move from unreadable -> readable state, but I couldn't say whether that's synchronous with the command returning. The replSetInitiate command traditionally returns with an operationTime that matches the "initiating replica set" oplog entry (and clusterTime, but I'm not sure if that's really a guarantee), which I think is worth keeping. From the perspective of what |
| Comment by Jack Mulrow [ 22/Mar/21 ] |
|
The goal of I backported |
| Comment by Daniel Gottlieb (Inactive) [ 22/Mar/21 ] |
|
Also jack.mulrow, can you confirm that without any changes, the same behavior to omit cluster times will show up in the next releases of 4.4 and 4.0? |
| Comment by Daniel Gottlieb (Inactive) [ 22/Mar/21 ] |
|
Hey anna.henningsen, thanks for filing a ticket. I'm able to reproduce/confirm the mongod server sends this response back in 4.2.13. I've traced this back to |