[DOCS-14283] [SERVER] Investigate SERVER-50827: Nodes with IP addresses in split horizons are unable to start Created: 10/Mar/21  Updated: 13/Nov/23  Resolved: 20/Jan/22

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 5.0.0-rc0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Dave Cuthbert (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-50827 Nodes with IP addresses in split hori... Closed
Participants:
Days since reply: 2 years, 48 weeks ago
Epic Link: DOCSP-15042

 Description   

Description

Downstream Change Summary

Following points should be added to documentation:

  • when configuring cluster for split horizon, IP addresses should not be used instead of host names
  • configuration when IP address is used for a host name will be rejected
  • it is possible to override such behavior using disableSplitHorizonIPCheck=true parameter
  • if cluster configuration is found to have an IP address in split horizon during cluster startup, the error would not prevent node from starting. This is done for scenarios when a node that is already configured was recently upgraded. Configuration changes happening after startup will still be rejected

Description of Linked Ticket

SERVER-49081 made it so that the replSetInitiate or replSetReconfig commands would be unable to accept IP addresses in their split horizon definitions, unless a special setParameter was toggled.

Unfortunately, it introduced the check in a validation function which is exercised at startup. This prevents nodes with IP addresses in their split horizon definitions from starting up.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)


Generated at Thu Feb 08 08:10:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.