What does this failure look like in production?

In production this failure typically appears during the first tens-to-hundreds of training steps: loss curves become non-monotonic, validation metrics plateau above the baseline, and downstream checkpoints either diverge or fail to improve. Engineers frequently misread it as data drift when the underlying mechanism is repeated traffic to a specific listing endpoint caused continuous database queries on info_caches collection. Validating against the symptom list in this entry is the fastest way to confirm the diagnosis.

Is this a hardware or a software issue?

Infrastructure failures can look like either layer depending on the symptom. The discriminator is the resolution of the symptom to the recommended fix: if applying the steps under "How to fix it" eliminates the symptom, this is a software/configuration class issue regardless of the hardware it surfaced on. Repeat the fix on a fresh node to confirm.

How long does the fix typically take?

Most resolutions from this entry take 10 to 30 minutes of engineer time once the diagnosis is confirmed. Long fixes come from skipping the diagnosis step and chasing apparent symptoms (validation drift, memory growth, slow throughput) instead of the actual root cause listed above. Apply the fix in a small experiment first, then roll it forward.

Does this affect inference or only training?

Primarily this is a infrastructure failure observed during training, but the same misconfiguration can leak into downstream evaluation and serving. Treat the prevention checklist as a guardrail: any pipeline that touches a trained checkpoint should re-validate the failure mode before promoting the model.

What's the cheapest way to confirm this is the problem?

Cheapest signal: reproduce the symptom on a 1-GPU toy run with the same configuration. If the toy run exhibits the same behavior, the cause is the configuration rather than the cluster. If only the multi-GPU run is affected, the failure is a distributed interaction, so MongoDB-backed web application with highly concurrent cache-miss traffic is the most likely layer to inspect.

Can the Denpex platform detect this automatically?

Yes. Denpex correlates the symptoms in this entry against your training logs in real time and surfaces the failure taxonomy, root cause, and exact remediation command on the console. Three full diagnoses are included free during signup, and the encyclopedia entry you are reading is generated from the same signal library that powers the platform.

What related failures should I check next?

Closely related failures cluster around #huggingface, #mongodb, #cache. After applying this fix, validate against the related entries below to confirm no overlapping cause is masking as this one. Engineers routinely discover that the dominant failure mode is actually a second, sibling failure compounded on top.

Will this recur after the fix?

Applied once with the prevention checklist, this failure does not recur under normal operation. The recurring variant most engineers encounter is the re-emergence of the same symptom on a different model or stack after huggingface is upgraded. Pin compatible versions and rerun the prevention smoke test on every dependency change.

Is there a fingerprint I can monitor?

Yes. MongoDB metrics show _info_cache collections with 10x normal query volume and >5s p99 latency is the highest-signal fingerprint. Wire a metric or alert on that signal (or its absence after the fix) so you can detect the recurrence automatically. The Denpex platform encodes this exact fingerprint and surfaces it directly in the dashboard.

What is the official documentation that covers this?

Reference documentation is listed in the References section at the bottom of this entry. The most authoritative URLs are the upstream framework docs and the issue trackers cited; the Denpex entry synthesizes both into the executive, engineer, and on-call perspectives so each audience can act without reading every linked source.

Does this entry include working code?

Yes. The "Code Examples" section contains copy-paste-ready snippets that target the most common stacks (PyTorch, Hugging Face Trainer, DeepSpeed, Megatron-LM, vLLM/Transformers). Each snippet is annotated with why it works so you can adapt the pattern to your own framework without losing fidelity.

MongoDB Info Cache Collection Queries Overloading Database During HuggingFace Hub Outage

Q: How does this scale from 1 GPU to 1000 GPUs?

At single-GPU scale the symptom usually looks like slow convergence or a single anomalous loss value. At 64+ GPU scale, distributed interactions amplify repeated traffic to a specific listing endpoint caused continuous database queries on info_caches collection through collectives, and the failure can manifest as a full job abort. Always reproduce the fix at the smallest cluster configuration that still exhibits the symptom before promoting to production scale.

The Hugging Face Hub suffered an extended 36-hour outage when repeated requests to space_info_cache and datasets_info_cache MongoDB collections overloaded the database cluster. A script repeatedly querying a specific Space listing URL triggered a cascade: increased MongoDB network I/O, replica lag, and ultimately complete database cluster failure. The outage required multiple waves of mitigation over two days.

Quick answer

The Hugging Face Hub suffered an extended 36-hour outage when repeated requests to space_info_cache and datasets_info_cache MongoDB collections overloaded the database cluster.

Root cause: Repeated traffic to a specific listing endpoint caused continuous database queries on info_caches collection. Each request missed cache and triggered a full MongoDB query, creating a snowball effect as more requests queued. Collections lacked query-level timeouts or circuit breakers; slow queries accumulated and exhausted connection pool.
Recommended fix: maxTimeMS=5000
How Denpex helps: Denpex investigates MongoDB Info Cache Collection Queries Overloading Database During HuggingFace Hub Outage using the evidence you provide or your connected workload collects. Earlier rank, host or application evidence is needed to distinguish an initiating failure from a downstream report.

Infrastructure#huggingface#mongodb#cache#database-outage#snowball-effect#redis

What this failure is

MongoDB Info Cache Collection Queries Overloading Database During HuggingFace Hub Outage is a Infrastructure failure seen during ML training runs. The Hugging Face Hub suffered an extended 36-hour outage when repeated requests to space_info_cache and datasets_info_cache MongoDB collections overloaded the database cluster. A script repeatedly querying a specific Space listing URL triggered a cascade: increased MongoDB network I/O, replica lag, and ultimately complete database cluster failure. The outage required multiple waves of mitigation over two days. Common tags: Huggingface, Mongodb, Cache, Database Outage.

Live diagnosis, no signup

Is this what broke your run? Paste your log.

You're reading about MongoDB Info Cache Collection Queries Overloading Database During HuggingFace Hub Outage. Paste your own traceback and relevant evidence for an investigation of your workload, with a next action or a specific missing fact. A reference entry does not establish your cause. No account or card for the free diagnosis. Review data handling before submitting sensitive logs.

Before uploading, review cloud data handling and local options.

training_logs.txt

No log to hand? Try one:

Upload or drop a plain-text log

Upload your log file. Large files are processed in your browser. Only selected evidence is submitted when you run diagnosis.

3 free diagnoses/day

Why it happens (the mechanism)

Repeated traffic to a specific listing endpoint caused continuous database queries on info_caches collection. Each request missed cache and triggered a full MongoDB query, creating a snowball effect as more requests queued. Collections lacked query-level timeouts or circuit breakers; slow queries accumulated and exhausted connection pool. Taken together, these mechanisms explain why the failure is reproducible, why it tends to surface on specific workloads or scales, and why generic mitigation attempts often fall short without addressing the underlying cause.

What you'll observe

MongoDB cluster becomes unresponsive under read load from info_cache collections
Database network-out bandwidth saturates, causing replica lag across cluster
Hub website slows to crawl or returns errors for all users

Common symptoms and what they mean

Symptom	Why it happens
MongoDB metrics show _info_cache collections with 10x normal query volume and >5s p99 latency	Repeated traffic to a specific listing endpoint caused continuous database queries on info_caches collection
Database network out spikes to 5x baseline, correlating with traffic to specific Space URLs	Each request missed cache and triggered a full MongoDB query, creating a snowball effect as more requests queued
MongoDB primary node CPU at 100% with connection queue filling	Collections lacked query-level timeouts or circuit breakers; slow queries accumulated and exhausted connection pool

Which systems are affected

MongoDB-backed web application with highly concurrent cache-miss traffic
Kubernetes services where API server rate limiting can cascade to downstream databases
Infrastructure with shared caches across multiple product surfaces (Spaces, Datasets, Models)

How to confirm this is the problem

Use this checklist to test the hypothesis against a small reproduction. No single line proves the root cause, so preserve the preceding events and compare one variable at a time.

✓Reproduce the failure from a clean checkpoint/seed: the symptom must appear without warm-up state from a previous run.
✓Verified signal present: MongoDB metrics show _info_cache collections with 10x normal query volume and >5s p99 latency
✓Verified signal present: Database network out spikes to 5x baseline, correlating with traffic to specific Space URLs
✓Verified signal present: MongoDB primary node CPU at 100% with connection queue filling
✓A targeted fix from the "How to fix it" section eliminates or substantially reduces the symptom within one validation pass.

Root cause

Repeated traffic to a specific listing endpoint caused continuous database queries on info_caches collection
Each request missed cache and triggered a full MongoDB query, creating a snowball effect as more requests queued
Collections lacked query-level timeouts or circuit breakers; slow queries accumulated and exhausted connection pool

The fix and how to prevent it

The fix and the prevention pattern

The root cause is on this page and stays free. A free account adds the exact remediation steps, saved history, and the fix on every entry in the encyclopedia.

No credit card. Daily allowance follows verified trust tier. Instant access.

Diagnose this failure in VS Code

Select the traceback or open the failed terminal, then run Denpex locally to see the initiating rank, collateral failures, exact fix, and verification command without uploading the log.

Install the free VS Code extension