Document biz_state light/heavy collect timeout env vars.

Add dual-lane READ vs RUN_TIMEOUT_CAP notes to .env.example and WEB.md so operators can raise the ~40min heavy cap.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
oliver 2026-09-22 19:14:16 +08:00
parent 924f9bd2f7
commit b453c6871e
2 changed files with 14 additions and 0 deletions

View file

@ -75,6 +75,15 @@ NETX_UME_NOTIFICATION_TOPIC=ALARM
# NETX_BIZ_STATE_WORKER_REPLICAS=2
# NETX_BIZ_STATE_SPOOL_DIR=data/biz_state_spool
# NETX_BIZ_STATE_PERSIST_EVERY_CMDS=8
# Dual-lane CLI timeouts (light = shared SSH; heavy = interface/route/MAC etc.):
# READ = per-command wait; RUN_TIMEOUT_CAP = whole-lane wall clock (often the ~40min abort).
# Light lane reuses NE collect defaults below (read 120s / cap 600s ≈ 10min).
# NETX_NE_COLLECT_READ_TIMEOUT_SEC=120
# NETX_NE_COLLECT_RUN_TIMEOUT_CAP_SEC=600
# Heavy lane defaults (raise CAP if batches end around 40min as partial/timeout):
# NETX_BIZ_STATE_HEAVY_READ_TIMEOUT_SEC=1500
# NETX_BIZ_STATE_HEAVY_RUN_TIMEOUT_CAP_SEC=2400
# NETX_BIZ_STATE_HEAVY_WORKERS=4
# --- Multi-user shared-server capacity (defaults in Settings already match these) ---
# NETX_DB_POOL_SIZE=40
# NETX_DB_MAX_OVERFLOW=40