[SERVER-28990] when started with --repair mongod should not try to bind to a port Created: 26/Apr/17 Updated: 30/Oct/23 Resolved: 17/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.3, 4.1.3 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Asya Kamsky | Assignee: | Annie Black |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | dev_tools, neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Backport Requested: |
v4.0
|
||||||||||||||||||||
| Sprint: | Platforms 2018-08-27, Platforms 2018-09-10, Platforms 2018-09-24 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Currently, when started with --repair mongod will exit after attempting to repair the data files, but it still tries to bind to a port:
This happens with all storage engines. After --repair mongod will shut down so it doesn't make sense that it should need to listen to a port since it won't accept any connections anyway. |
| Comments |
| Comment by Githook User [ 24/Sep/18 ] |
|
Author: {'name': 'Annie Black', 'email': 'annie.black@10gen.com', 'username': 'ablack12'}Message: (cherry picked from commit 8084a0ce51f6af543385e9292d11b6943d6b7cd4) |
| Comment by Githook User [ 12/Sep/18 ] |
|
Author: {'name': 'Annie Black', 'email': 'annie.black@10gen.com', 'username': 'ablack12'}Message: |