[SERVER-15499] Confusion with error message "Assertion: 13110:HostAndPort: host is empty" when all data bearing nodes in shard are down Created: 02/Oct/14 Updated: 06/Dec/22 Resolved: 16/Nov/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.4.10 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Eoin Brazil | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
OS: Linux ip 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u3 x86_64 GNU/Linux |
||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||
| Operating System: | Linux | ||||||||||||
| Steps To Reproduce: | Setup 2 shards across EC2 N.Virginia and Ireland EU-West with 1P 1A (replicaset default-s1) 1S (replicaset foo-s1) In EU-West I killed using SIGTERM the following: On the Mongos via the MongoShell then enter:
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
Hi All, There is some confusion with the error message:
In the scenario where all of the data bearing nodes within a specific shard are down, this assertion message can cause confusion. Is it possible to refactor the error message from "HostAndPort: host is empty" for cases where all data bearing nodes in a replicaset are down/unavailable ? Thanks! |
| Comments |
| Comment by Ramon Fernandez Marina [ 02/Oct/14 ] | |||||||||
|
I'm not able to trigger that error. I created a setup like the one described above, and when if I try to insert a document into an empty database I get:
If the database already exists, I get:
I get the errors above when terminating data bearing nodes one at a time with a pause in between. If I terminate them at the same time then the error message is different:
So I wonder if something else is going on that's triggering the assertion you're seeing. Note also that the "HostPort" assertion may be triggered by other situations, so I don't think changing it to match this specific scenario will help as it will make other scenarios confusing. |