[SERVER-28949] Make JSTests use the localhost network interface Created: 24/Apr/17 Updated: 06/Dec/22 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | features we're not sure of |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Jackson | Assignee: | Backlog - Security Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Server Security
|
||||||||
| Participants: | |||||||||
| Description |
|
There may be benefits to making these nodes bind to localhost. localhost connections can incur less latency, as the kernel can bypass chunks of the networking stack. These chunks may be larger in virtualized environments like AWS. |
| Comments |
| Comment by Andy Schwerin [ 25/Apr/17 ] |
|
Before changing this, investigate how it affects coverage. The tests intentionally used the public IP address, at least historically, because it exercised different logic in the replication and sharding code. Until we are confident that we have excised that code, we should keep existing behavior. |