Repository navigation
Keep File Search syncs calm when the extractor restarts; worker healthcheck (#1383) - #1400
Merged
Merged
Conversation
…hcheck (#1383) An extractor restart (deploy or memory limit) ended the sync as failed; it is now a partial run that continues in two minutes. files-worker had the backend's healthcheck (port 4000) and always showed unhealthy; it now probes its own /internal/health. Lower memory defaults: worker heap 512 MB, extractor 1.5 GB on the Cloud.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Found while monitoring File Search on the Cloud (2026-11-01, after lowering the extractor's memory limit).
file-extractor(a deploy, or its memory limit) ended the running sync as failed in the Files panel, although no file was at fault. It is now a partial run with a clear message, and the sync continues in two minutes (was five). No file is penalised, as before.files-workerinherited the image's healthcheck, which probes the backend on:4000, so it always showedunhealthy. It now probes its own/internal/healthwith the worker token.FILES_WORKER_MAX_OLD_SPACE_MB. The worker container stays at 1 GB, because on Enterprise two syncs can each hold a 200 MB file.Cloud and self-hosted behave the same; only the Cloud's extractor default differs.
Type
Testing
packages/backendnpx tsc --noEmit -p tsconfig.jsonpackages/backendnpx jest src/ee/file-search src/file-search --maxWorkers=4docker compose -f docker-compose.cloud.yml config -q, same fordocker-compose.ymlwgetwithX-Worker-Tokento/internal/health)HEALTH_OKRelated Issues
Relates to #1383, #1379.