mcp-server

42 Commits 2 Branches 0 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
Claude	6bcf3b9ac9	feat: run FastAPI under gunicorn with uvicorn ASGI workers Production entrypoint switch: - pyproject.toml: add gunicorn>=23.0 dep - gunicorn.conf.py: env-var-driven config (bind, workers, threads, timeout, graceful_timeout, keepalive, log level, access-log format) - Dockerfile: CMD gunicorn main:app (auto-loads gunicorn.conf.py from WORKDIR /app) - docker-compose.yml: forward GUNICORN_WORKERS / GUNICORN_TIMEOUT / GUNICORN_BIND - .env.example: document the new tunables Why gunicorn over standalone uvicorn for production: - Process supervision: master restarts crashed workers, restarts on memory leaks - Graceful shutdown: SIGTERM drains workers in-flight - Multi-worker: concurrent requests actually run in parallel - Standard ops: k8s readiness probes, log aggregators, etc. all know gunicorn Why uvicorn workers (not sync workers): gunicorn can't natively serve ASGI; uvicorn.workers.UvicornWorker is the canonical way to run an ASGI app under gunicorn. Defaults: - 2 workers (small MCP service; raise for high concurrency) - 1 thread per worker (no blocking I/O) - 120s timeout (yarn logs can be slow; uvicorn's 30s default is too tight) Verified: gunicorn boots, lifespan runs (14 tools logged), MCP initialize + tools/list + tools/call all work, /openapi.json = 200, multiple gunicorn worker processes visible in ps. uv sync picked up gunicorn 26.0.0. Tests still 116/116.	2026-06-25 10:44:25 +08:00
Claude	504447048d	feat(docker-compose.yml): remove healthcheck	2026-06-24 18:23:15 +08:00
Claude	ce8dc1e2ba	feat: add docker-compose.yml + .env.example docker-compose.yml: - Builds the Dockerfile, exposes :8000 - Mounts ./data (persistent) and ./hadoop-conf (ro) for cluster configs - Forwards YARN_RESOURCE_MANAGER_URL via env var (fallback for REST client) - Healthcheck via /openapi.json (cheap liveness probe; MCP initialize handshake would be more accurate but requires session-id plumbing) - restart: unless-stopped for production - Resource limit section commented out (server itself is lightweight) .env.example: - Documents the env vars compose expects - .env is gitignored	2026-06-24 18:20:16 +08:00

Author

SHA1

Message

Date

Claude

6bcf3b9ac9

feat: run FastAPI under gunicorn with uvicorn ASGI workers

Production entrypoint switch:
  - pyproject.toml: add gunicorn>=23.0 dep
  - gunicorn.conf.py: env-var-driven config (bind, workers, threads,
    timeout, graceful_timeout, keepalive, log level, access-log format)
  - Dockerfile: CMD gunicorn main:app (auto-loads gunicorn.conf.py from
    WORKDIR /app)
  - docker-compose.yml: forward GUNICORN_WORKERS / GUNICORN_TIMEOUT /
    GUNICORN_BIND
  - .env.example: document the new tunables

Why gunicorn over standalone uvicorn for production:
  - Process supervision: master restarts crashed workers, restarts on
    memory leaks
  - Graceful shutdown: SIGTERM drains workers in-flight
  - Multi-worker: concurrent requests actually run in parallel
  - Standard ops: k8s readiness probes, log aggregators, etc. all know
    gunicorn

Why uvicorn workers (not sync workers): gunicorn can't natively serve
ASGI; uvicorn.workers.UvicornWorker is the canonical way to run an
ASGI app under gunicorn.

Defaults:
  - 2 workers (small MCP service; raise for high concurrency)
  - 1 thread per worker (no blocking I/O)
  - 120s timeout (yarn logs can be slow; uvicorn's 30s default is too
    tight)

Verified: gunicorn boots, lifespan runs (14 tools logged), MCP
initialize + tools/list + tools/call all work, /openapi.json = 200,
multiple gunicorn worker processes visible in ps.

uv sync picked up gunicorn 26.0.0. Tests still 116/116.

2026-06-25 10:44:25 +08:00

Claude

504447048d

feat(docker-compose.yml): remove healthcheck

2026-06-24 18:23:15 +08:00

Claude

ce8dc1e2ba

feat: add docker-compose.yml + .env.example

docker-compose.yml:
- Builds the Dockerfile, exposes :8000
- Mounts ./data (persistent) and ./hadoop-conf (ro) for cluster configs
- Forwards YARN_RESOURCE_MANAGER_URL via env var (fallback for REST client)
- Healthcheck via /openapi.json (cheap liveness probe; MCP initialize
  handshake would be more accurate but requires session-id plumbing)
- restart: unless-stopped for production
- Resource limit section commented out (server itself is lightweight)

.env.example:
- Documents the env vars compose expects
- .env is gitignored

2026-06-24 18:20:16 +08:00