Files
document-haness/docs/clean-architecture-backend-template/tech-log-studio/delivery-and-settlement-models/concept/concept-grpc-admin-c01.md
T
DongHyeonkaandClaude Opus 5 b2963105a8 docs(keycloak-session-store): import the session-storage lab as a new project
The keycloak project ended with four open questions that design could not
settle. A two-VM lab was built to answer them by measurement, and this is
that material: 26 experiments, 125 raw command outputs, 22 browser captures.

Follows the import procedure in README.md.

  source/     the originating repository verbatim — 78 documents, 28 SVGs,
              8 manifests, plus .source-revision recording the commit
  final/      the SSOT
    document.md   729 lines written from the 29 experiment documents, not
                  concatenated: what was predicted, what was measured, and
                  where the measurement itself was wrong
    evidence/raw    125 outputs, flattened to <experiment>__<file> because
                    the originals collided (01-baseline.txt appeared three
                    times) and the audit only globs the top level
    evidence/meta   one per raw file; command and exitCode are null and the
                    README says why rather than inventing them
    evidence/browser  22 captures
    assets/       three diagrams through techviz
    .techviz/     their VizSpecs

A separate project rather than an addition to keycloak: the B-layer answers
that project's four questions, but the A, C and D layers are about cluster
failure, SSO and operations, and one document.md should hold one subject.
The four question records there can point here through 관계.

Recorded rather than papered over: only three of the 28 diagrams were
remade. The repository forbids hand-drawn SVG and forbids titles inside the
canvas; all 28 originals carry both, so converting them is redrawing, not
reformatting. They stay in source/ and the gap is written into the document.

verify-pipeline.py passes. audit-records.py reports no issues.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-04 22:51:59 +09:00

54 lines
2.2 KiB
Markdown

---
kind: CONCEPT
slug: grpc-admin-c01
title: 건강 레지스트리 — 낙관에서 시작하지 않는다
topic: delivery-and-settlement-models
project: clean-architecture-backend-template
status: 게시 전
sourceRevision: 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916
rootTreeNode: concept:grpc-admin-c01
evidenceCapturedOn: 2026-09-01
assets:
- key: grpc-admin-c01
file: ../../../final/evidence/rendered/grpc-admin-c01.svg
- key: grpc-admin-c01-diagram
file: ../../../final/assets/diagrams/grpc-admin-c01.svg
evidence:
- ../../../final/evidence/raw/grpc-admin-c01.txt
source:
- 원본 분석 절은 analysis/grpc/grpc-admin.md#L50 이다.
module: grpc-admin
---
# 건강 레지스트리 — 낙관에서 시작하지 않는다
모든 등록 서비스가 UNKNOWN 에서 시작한다. 그리고 배수 중에는 markServing·markNotServing 이 무시된다.
## 본문
<!-- body:start -->
모든 등록 서비스가 `UNKNOWN` 에서 시작한다.
> "A registry that starts optimistic reports ready during startup, receives traffic before the first dependency check has run, and fails the requests that arrive in that window — the window being exactly the moment a rollout is shifting traffic onto the instance."
## 배수 중에는 표시가 무시된다
`markServing`·`markNotServing` 이 무시된다.
> "a service that reports itself healthy after the drain has started would be routed traffic the instance has already promised not to take."
## 전역 상태 판정 우선순위
:::evidence key="grpc-admin-c01-diagram" alt="임계 의존 불건강과 하나라도 NOT_SERVING 과 하나라도 SERVING 과 그 밖이 위에서 아래로 쌓여 있고 오른쪽에 판정 순서 화살표가 있다" caption="전역 상태 판정 우선순위" zoom="false"
:::
임계 의존이 하나라도 불건강하면 `NOT_SERVING`, 아니면 하나라도 `NOT_SERVING` 이면 `NOT_SERVING`, 하나라도 `SERVING` 이면 `SERVING`, 그 밖에는 `UNKNOWN` 이다.
## 이 기록이 다루는 범위
:::evidence key="grpc-admin-c01" alt="코드베이스에서 파일 목록을 만든 출력 13줄. 이 기록이 다루는 범위가 그 목록이다." caption="코드베이스 파일 목록 — 13줄 · exit 0" zoom="true"
:::
<!-- body:end -->