[SERVER-3507] Changing hostname in Replica Set configuration, does not affect rs.status(), until a server restart. Created: 31/Jul/11 Updated: 29/May/12 Resolved: 31/Jul/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 1.8.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Shlomo Priymak | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Solaris 11 (Express) |
||
| Issue Links: |
|
||||||||
| Operating System: | Solaris | ||||||||
| Participants: | |||||||||
| Description |
|
When initiating a replica set using rs.initiate(), the resulting rs.conf() object has the local hostname in it. When changing it to the fully qualified domain name using this method: conf = rs.conf() the resulting rs.conf() object is updated with the new domain name. Alas, rs.status() reports the old hostname. This problem affects, for example, connecting java clients to the server which need the FQDN to function. These read the slave/master information from the replica status object, and pay no attention to rs.conf(). |
| Comments |
| Comment by Brennan Pang [ 27/Feb/12 ] |
|
I recently encountered this same issue in 1.8.3. |
| Comment by Scott Hernandez (Inactive) [ 31/Jul/11 ] |
|
This has been fixed already for 1.8.3/+. |