<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Connection-Draining on CharmingGroot</title>
    <link>https://charminggroot.github.io/tags/connection-draining/</link>
    <description>Recent content in Connection-Draining on CharmingGroot</description>
    <generator>Hugo</generator>
    <language>ko-kr</language>
    <lastBuildDate>Sat, 13 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://charminggroot.github.io/tags/connection-draining/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>043. Health Check &amp; Connection Draining — 로드밸런서의 무중단 배포 기반</title>
      <link>https://charminggroot.github.io/posts/043-health-check-connection-draining/</link>
      <pubDate>Sat, 13 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://charminggroot.github.io/posts/043-health-check-connection-draining/</guid>
      <description>로드밸런서는 헬스체크로 서버가 정상인지 확인하고, 비정상 서버로는 트래픽을 보내지 않는다. Connection Draining은 서버를 내릴 때 기존 연결을 끊지 않고 자연스럽게 처리가 끝나길 기다린다. 이 두 메커니즘이 무중단 배포와 자동 장애 복구의 기반이 된다.</description>
    </item>
  </channel>
</rss>
