[SERVER-35350] Add a way to detect when mongobridge is ready to accept connections after startup Created: 01/Jun/18 Updated: 06/Dec/22 Resolved: 05/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | William Schultz (Inactive) | Assignee: | Backlog - Server Tooling and Methods (STM) (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | stm, tig-mongobridge | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Server Tooling & Methods
|
||||||||
| Participants: | |||||||||
| Linked BF Score: | 71 | ||||||||
| Description |
|
There is a period of time after a mongobridge process starts up but before it is ready to accept connections. If a mongod server tries to connect to the mongobridge in this period, it will fail. This can be a problem, for example, when we restart a mongobridge and its associated mongod server in a replica set test. If we restart the mongobridge, and then restart the mongod, the mongod replica set node will try to identify itself by calling _isSelf against the mongobridge host. If the mongobridge is not ready to accept connections yet, then the command will fail, causing the node to consider itself removed from the replica set config. We should have some way to make sure the mongobridge is ready to accept connections in our tests. |
| Comments |
| Comment by Brooke Miller [ 05/Nov/21 ] |
|
We're not planning to invest in mongobridge at this time, so closing this as won't fix. |