[SERVER-49157] Initialize WireSpec during MONGO_INITIALIZER Created: 26/Jun/20 Updated: 29/Oct/23 Resolved: 04/Aug/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benjamin Caimano (Inactive) | Assignee: | Amirsaman Memaripour |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | servicearch-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Sprint: | Service Arch 2020-07-27, Service Arch 2020-08-10 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
We default initialize the WireSpec on first use here. Unfortunately, this means that we can set isInternalClient late like we do here. We should formally initialize the global WireSpec with a MONGO_INITIALIZER. It would also be nice if we allowed a TransportLayer to reference a specific WireSpec. It would allow us to switch during our testing or have both internal and external clients in process. |
| Comments |
| Comment by Githook User [ 04/Aug/20 ] |
|
Author: {'name': 'Amirsaman Memaripour', 'email': 'amirsaman.memaripour@mongodb.com', 'username': 'samanca'}Message: |
| Comment by Githook User [ 29/Jul/20 ] |
|
Author: {'name': 'Amirsaman Memaripour', 'email': 'amirsaman.memaripour@mongodb.com', 'username': 'samanca'}Message: |
| Comment by Githook User [ 29/Jul/20 ] |
|
Author: {'name': 'Amirsaman Memaripour', 'email': 'amirsaman.memaripour@mongodb.com', 'username': 'samanca'}Message: |
| Comment by Mira Carey [ 30/Jun/20 ] |
|
I think my preference would be to make it unusable before init, and actually init it in the initializer graph after command line option parsing |