We terminated a TPU mid-training and it recovered in seconds: Introduction to elastic training with MaxText
Same process, same PID, under two minutes of downtime, and almost all of it was waiting for Kubernetes to schedule the replacement worker. It still has every entry from before the failure. That object lives in CPU memory on the controller, not on any TPU, so an elastic event can't touch it.
- ▪Same process, same PID, under two minutes of downtime, and almost all of it was waiting for Kubernetes to schedule the replacement worker.
- ▪It still has every entry from before the failure.
- ▪That object lives in CPU memory on the controller, not on any TPU, so an elastic event can't touch it.
Google Developers Blog files mainly under programming. We currently carry 20 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Google Developers Blog |
| Canonical URL | https://developers.googleblog.com/we-terminated-a-tpu-mid-training-and-it-recovered-in-seconds-introduction-to-elastic-training-with-maxtext/ |
| Publication time | Not provided by source |
| Retrieval time | 2026-07-25T23:18:53.148Z |
| Last seen | 2026-07-25T23:19:03.079Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | sdwLujbTl9Lw |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Zero restarts. Same process, same PID, under two minutes of downtime, and almost all of it was waiting for Kubernetes to schedule the replacement worker. For comparison, a full job restart on this same cluster pays for everything we just skipped: tearing down and rescheduling the entire workload — controller and all workers, not just the failed slice — sometimes a full termination grace period, then starting fresh containers and Python processes before it even gets to the checkpoint load.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Google Developers Blog.
Discussion
0 commentsMore from Google Developers Blog
