E3SM-Project / E3SM-Project/simboard

[DevOps]: Make site-ingestion lock contention reliable

Open
#334 1 comment 0 reactions 1 assignee Claimed by @TonyB9000 View on GitHub
type: devops
Dominant language
Python
Stars
1
Forks
2
Avg merge
25m
Merged PRs (30d)
14

Description

### Task Details

Split from #332. Ensure a staging run cannot silently cause the daily archive scan to be missed while preserving single-run access to ingestion state.

### Steps to Complete

- Define safe staging/archive lock-contention behavior.
- Ensure archive scans have a reliable non-overlapping window or safely wait for an active run.
- Make lock contention visible in job status and launcher logs.
- Add launcher tests for lock behavior.

### Additional Notes

- Preserve single-run serialization.
- Launcher: `backend/app/scripts/ingestion/sites/site_ingestion_launcher.sh`

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.