about summary refs log tree commit diff
path: root/test/python/test_dev_token.py
diff options
context:
space:
mode:
authorPjotr <wrk@bosa.lan>2026-11-14 22:42:11 +0000
committerPjotr <wrk@bosa.lan>2026-11-14 22:42:11 +0000
commit3a62ef34c127d36fd4e04583349f64eee5de2c6f (patch)
treee60085c1ae4c9e8f085cb23c3dc0767a0f0dfb18 /test/python/test_dev_token.py
parenta89781c2eaf4b503f416cc2aba2420cd15fa5289 (diff)
downloadgenenetwork4-3a62ef34c127d36fd4e04583349f64eee5de2c6f.tar.gz
ravanan-slurm: what happens when Slurm goes away
Measured against the slurm container, 20 chromosomes, 40 jobs: baseline
200/21 055 rows in 205.5 s; slurmrestd unreachable -> 502 in 3.7 s;
container killed 45 s into a request -> 502 in 50.2 s with 0 rows (no
partial results); the same request after Slurm returns -> 200 in 163.3 s,
i.e. the retry reuses the steps that had finished, because ravanan's store
lives in RAVANAN_CACHE_DIR and not in Slurm.
So: no automatic failover, no fallback to single-machine, nothing sticky,
and a retry that is cheaper than cold. The 502's detail is ravanan's Guile
backtrace, so the one useful line sits at its end; a pre-flight
/slurm/v0.0.41/ping would make that a 503 naming the endpoint, and there
is no timeout on the ravanan child for a Slurm that accepts connections
and never runs the job -- both recorded as gaps.
Diffstat (limited to 'test/python/test_dev_token.py')
0 files changed, 0 insertions, 0 deletions