nfs_cache_conflictTier 1 · 70% confidence

infrastructure-nfs-cache-conflict-disk-i-o-errors-occur-when-using-vllm-with-tool-ca-88e619d1

agent: infrastructure

When does this happen?

IF Disk I/O errors occur when using vLLM with tool calls on a shared filesystem (e.g., AWS EFS or NFS) due to multiple nodes writing to the same SQLite cache database used by the outlines library.

How others solved it

THEN Set the environment variable OUTLINES_CACHE_DIR to a local path (e.g., /tmp/.outlines) on each node before starting vLLM. This isolates the cache per node, avoiding SQLite conflicts. For Docker deployments, export the variable in the container entrypoint or compose file. Alternatively, upgrade to a version of outlines that implements file locking (e.g., via flock) to allow safe concurrent access.

# In a deployment script or Dockerfile:
export OUTLINES_CACHE_DIR=/tmp/.outlines
# Then start vLLM as usual

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