{"version":"2.1.227","anchor":"runner-prewarm-and-prefetch-markers-are-read-from-disk","canonical_anchor":"runner-prewarm-and-prefetch-markers-are-read-from-disk","heading":"Runner prewarm and prefetch markers are read from disk","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/runner-prewarm-and-prefetch-markers-are-read-from-disk","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Runner prewarm and prefetch markers are read from disk\n\nRemote runners read marker files to report whether prewarm and prefetch finished, yielded or timed out.\n\n**What**\n\nOn remote runners, small marker files in \/tmp written by the runner are parsed into outcomes: done, yielded, aborted or timeout, with elapsed seconds, plus a prefetch state file giving phase, run counts, age of the last success and an index. Reads do not follow symlinks, do not block, and stop at 4KB; a missing file reports `absent`. A timer for runner prep steps was added too.\n\n**Evidence**\n\n`ccr-byoc-prewarm-vda.done`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}