How we rebuilt the search architecture for high availability in GitHub Enterprise Server

GitHub has enhanced its Enterprise Server's search functionality, focusing on improving durability and reducing administrative burdens by integrating Elasticsearch's Cross Cluster Replication (CCR) feature. Historically, managing search indexes required precise maintenance to avoid issues like data locks, especially in High Availability (HA) setups where the primary and replica nodes operated under a leader/follower pattern. Previous versions faced challenges due to Elasticsearch's constraints, causing instability in the GitHub Enterprise Server. By transitioning to use single-node Elasticsearch clusters with CCR, GitHub now ensures that data replication is more reliable and that critical data does not end up on read-only nodes. This shift allows for better data management, as CCR copies data once it’s safely persisted. GitHub has developed custom workflows to facilitate this transition, including for failovers and upgrades. Administrators interested in this new architecture can contact GitHub support to enable the CCR mode, which is expected to become the default within two years, offering a more seamless experience for managing GitHub Enterprise Server.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.