[SERVER-21047] Error message in rs.add() is confusing, should be just "Connection refused" Created: 21/Oct/15 Updated: 06/Dec/22 Resolved: 31/Oct/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.2.0-rc0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Henrik Ingo (Inactive) | Assignee: | Backlog - Replication Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Participants: |
| Description |
The above error is simple: mongod isn't running on the node I'm attempting to add. The error message about quorum check is confusing. Two things need fixing or at least checking:
|
| Comments |
| Comment by sidhant mahajan [ 09/Mar/17 ] |
|
I got the same issue but in my case it is Ip is rightly specified. Still I am getting connection refused. "respond affirmatively: "172.31.42.223:27017 failed with Connection refused", |
| Comment by Henrik Ingo (Inactive) [ 23/Oct/15 ] |
|
My argument is from a usability point of view. You could allow to add nodes that don't currently exist, but is there any benefit for allowing that? On the other hand typoing the hostname/ip-address is a very likely error, shouldn't we optimize for a simple error message in that case? I realize my argument is subjective, this is a user experience feedback after having played with it. In theory (from an algorithm point of view) there's nothing wrong with the current behavior. |
| Comment by Eric Milkie [ 21/Oct/15 ] |
|
Why should there be a new restriction that the node be up when you add it? |