[SERVER-24620] Combine error codes HostNotFound and NodeNotFound Created: 16/Jun/16 Updated: 04/Oct/18 Resolved: 04/Oct/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.5 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Andy Schwerin | Assignee: | Annie Black |
| Resolution: | Done | Votes: | 0 |
| Labels: | neweng, service_architecture | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Platforms 2018-09-10, Service Arch 2018-10-08 |
| Participants: |
| Description |
|
These two error codes appear to mean the same thing. Worse, HostNotFound appears to never be returned outside of tests, but we have code that checks for it to make choices about operation retry. That code does not check for NodeNotFound, which at least could be returned, though may not be in practice. |
| Comments |
| Comment by Githook User [ 04/Oct/18 ] |
|
Author: {'name': 'ablack12', 'email': 'annie.black@10gen.com', 'username': 'ablack12'}Message: |