This Morning's Git Protocol Outage
Blog post from GitHub
Anonymous Git clones were offline for several hours due to an issue with HAProxy's session limit being reached after the removal of the client inactivity timeout, which led to idle connections consuming all available spots. This change was initially made to prevent incorrect severing of long-running RPC calls, but it inadvertently allowed unproductive connections to persist without data transfer, causing subsequent connections to be dropped. In response, the timeouts have been reinstated, and a more robust monitoring solution for the Git protocol is being implemented to ensure timely notifications of similar issues in the future. The incident highlights the importance of diligent monitoring and configuration management to maintain availability, and there is a commitment to preventing such problems from reoccurring.
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.