[SERVER-65103] incorrect HostAndPort alphabetical order Created: 30/Mar/22 Updated: 29/Oct/23 Resolved: 15/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Billy Donahue | Assignee: | Celina Tala |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Service Arch 2022-09-05, Service Arch 2022-09-19 |
| Participants: |
| Description |
|
The alphabetical order of HostAndPort entries is significant in targeting hedged reads.
I can see a few problems with this.
|
| Comments |
| Comment by Githook User [ 14/Sep/22 ] | |||
|
Author: {'name': 'Celina Tala', 'email': 'celinahtala@gmail.com', 'username': 'celinatala-1'}Message: | |||
| Comment by Billy Donahue [ 31/Mar/22 ] | |||
|
I didn't observe a problem caused by this in tests. I'm just reading the code. This could become an issue when running tests outside of Evergreen. In an Evergreen build host, I suppose all the servers are co-hosted and hostnames are going to be identical and the HostAndPort will only vary by port number. | |||
| Comment by Max Hirschhorn [ 31/Mar/22 ] | |||
|
My understanding of targetHostsInAlphabeticalOrder
is that it is only used to get a deterministic order of messages being dispatched for tests to assert results on. Do we know that the case-sensitivity or IPv6 address issues actually affect the behavior in practice in Evergreen? |