[SERVER-63998] Replicator always started on the same port Created: 25/Feb/22 Updated: 29/Oct/23 Resolved: 03/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Vishnu Kaushik | Assignee: | Jason Chan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | Replicator-Bugs | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Repl 2022-03-07 |
| Participants: |
| Description |
|
By default, the replicator is started on port 27182. Use resmoke's ability to get a new port to set the port instead, otherwise multiple replicators cannot run on the same machine as they can't bind to the same port. This can be fixed by setting the --port CLI option when the ClusterToClusterFixture is set up. To get a port that is not in use, we can ask resmoke to give us one. See comments for example patch build. |
| Comments |
| Comment by Githook User [ 01/Mar/22 ] |
|
Author: {'name': 'Jason Chan', 'email': 'jason.chan@mongodb.com', 'username': 'jasonjhchan'}Message: |