[SERVER-33585] Do not return $clusterTime when no keys are available Created: 01/Mar/18 Updated: 29/Oct/23 Resolved: 26/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.5, 3.7.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Misha Tyulenev | Assignee: | Misha Tyulenev |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Backport Requested: |
v3.6
|
||||||||||||||||||||
| Sprint: | Sharding 2018-03-26, Sharding 2018-04-09 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
The problemThere are occasional errors while starting up mongodb replica set detailed in The solutionIts ok to not return $clusterTime if there are no keys available. The internal clients always use the internal user to communicate to each other - its a different code path. Returning no signature to external clients only in the case when auth is on will fix problems in |
| Comments |
| Comment by Githook User [ 11/May/18 ] |
|
Author: {'name': 'Misha Tyulenev', 'email': 'misha@mongodb.com', 'username': 'mikety'}Message: |
| Comment by Githook User [ 26/Mar/18 ] |
|
Author: {'email': 'misha@mongodb.com', 'name': 'Misha Tyulenev', 'username': 'mikety'}Message: |
| Comment by Bernie Hackett [ 01/Mar/18 ] |
|
This ^. Drivers know how to handle not getting a cluster time. They can't handle getting a broken cluster time. |
| Comment by Shane Harvey [ 01/Mar/18 ] |
|
What if the dummy $clusterTime is never sent to external clients but is still sent internally to mongod/mongos so that the replica set can start properly? |