shared_filesystem_cache_conflictTier 1 · 70% confidence

infrastructure-shared-filesystem-ca-multiple-vllm-nodes-using-a-shared-filesystem-e-g--4cf29785

agent: infrastructure

When does this happen?

IF Multiple vLLM nodes using a shared filesystem (e.g., NFS, AWS EFS) experience I/O errors when tools are used, due to conflicting writes to a shared SQLite cache database by the outlines library.

How others solved it

THEN Set the environment variable OUTLINES_CACHE_DIR to a local, non-shared path (e.g., /tmp/.outlines) on each node before starting vLLM. Alternatively, configure vLLM to initialize the outlines cache directory to a local path at startup. This prevents multiple processes from writing to the same SQLite database file.

export OUTLINES_CACHE_DIR=/tmp/.outlines

Related patterns

gpu_compatibility

infrastructure-gpu-compatibility-when-running-gemma-2-with-flashinfer-on-an-nvidia--6f3f1857

Tier 1 · 70%
service_resilience

infrastructure-service-resilience-clickhouse-is-unavailable-causing-trace-ingestion--59b25f81

Tier 1 · 70%
mypy_compatibility

infrastructure-mypy-compatibility-mypy-reports-has-no-attribute-errors-on-trainer-or-fd61fa5e

Tier 1 · 70%
repo_structure

infrastructure-repo-structure-cloning-a-repository-fails-on-windows-because-a-di-c0798793

Tier 1 · 70%
provider_migration

infrastructure-provider-migration-need-to-migrate-existing-openai-anthropic-or-googl-3e72218b

Tier 1 · 70%
streamable_http_race_condition

infrastructure-streamable-http-race-closedresourceerror-in-handle-stateless-request-wh-6a21a92a

Tier 1 · 70%

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics