zhangwenjian adcdd2edcd docs📝: name the job scheduler as the other reason for one replica ...

The comment on replicas gave one obstacle to raising it, the shared log
volume, which reads as the only one. Someone who moves the log path off
that volume would conclude the way is clear.

The scheduler in app/jobs is the second, and it is the one that does not
announce itself. Its handle on a job lives in sys_job.entry_id, one
column shared by every process, and startup zeroes the whole column
before writing its own ids. A second pod therefore erases the first
pod's, and both pods run the full enabled list. Stopping a job from the
UI then removes an entry from whichever process is asked, by an id that
belongs to another one, and answers 200.

See #915.

2026-09-07 13:32:43 +08:00

..

k8s

docs📝: name the job scheduler as the other reason for one replica

2026-09-07 13:32:43 +08:00

Dockerfile

feat ✨ 验证码store支持go-admin cache

2021-04-08 21:33:36 +08:00