[SERVER-29652] mongos should not gossip $logicalTime until admin.system.keys are created Created: 15/Jun/17 Updated: 30/Oct/23 Resolved: 22/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.10 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Misha Tyulenev | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding 2017-06-19, Sharding 2017-07-10 | ||||||||
| Participants: | |||||||||
| Description |
|
In shards and config servers the featureCompatibilityVersion is available. This is however not the case for mongos which is currently uses the featureCompatibilityVersion correlated to its binary. This causes a problem in causal consistency as mongos will be trying to sign the outgoing requests and will block waiting on the keys. This is not acceptable as the upgrade process may take very long time. Its possible that user upgrade the binaries but never issue setFeatureCompatibilityVersion command. So polling is not a good idea for mongos to discover its version. This way mongos will eventually start using causal consistency within 10 minutes of actual upgrade. |
| Comments |
| Comment by Githook User [ 23/Jun/17 ] |
|
Author: {u'username': u'jsmulrow', u'name': u'Jack Mulrow', u'email': u'jack.mulrow@mongodb.com'}Message: |
| Comment by Githook User [ 22/Jun/17 ] |
|
Author: {u'username': u'jsmulrow', u'name': u'Jack Mulrow', u'email': u'jack.mulrow@mongodb.com'}Message: |
| Comment by Githook User [ 22/Jun/17 ] |
|
Author: {u'username': u'jsmulrow', u'name': u'Jack Mulrow', u'email': u'jack.mulrow@mongodb.com'}Message: |