Skip to content
Tagged articles

Crash Recovery

27 articles · Page 1 of 1
JD Tech
JD Tech
Oct 22, 2026 · Databases

Five Layers of Database High Availability: From WAL to Orchestrator Auto-Failover

This article systematically breaks down database high availability into five layers — single-node durability via WAL and two-phase commit, master-slave replication with async and semi-sync modes, GTID-based global transaction identification, consistent failover with fencing, and automated failover using Orchestrator and probe-agent — illustrating each with real-world failure cases and configuration details.

Crash RecoveryFailoverGTID
0 likes · 25 min read
Five Layers of Database High Availability: From WAL to Orchestrator Auto-Failover
JD Tech Talk
JD Tech Talk
Oct 22, 2026 · Databases

Database High Availability: 5-Layer Architecture from WAL to Automated Failover

This article details a five-layer database high availability architecture: single-node crash recovery via WAL and two-phase commit, asynchronous and semi-synchronous replication trade-offs, GTID-based global transaction identification for seamless failover, fencing mechanisms to prevent split-brain, and Orchestrator with probe-agent for automated failure detection and failover execution.

Crash RecoveryFailoverFencing
0 likes · 26 min read
Database High Availability: 5-Layer Architecture from WAL to Automated Failover
JD Cloud Developers
JD Cloud Developers
Oct 22, 2026 · Databases

Database HA Deep Dive: Five Layers from WAL to Automated Failover

This article systematically explains database high availability through five layers: single-node crash recovery via WAL and two-phase commit, replication modes (async vs semi-sync) and RPO trade-offs, GTID-based global transaction identification for safe failover, fencing and PRS/ERS switching protocols to prevent split-brain, and Orchestrator's cross-check failure detection with probe-agent for automated failover.

Crash RecoveryFailoverGTID
0 likes · 28 min read
Database HA Deep Dive: Five Layers from WAL to Automated Failover
AI Engineering
AI Engineering
Oct 20, 2026 · Artificial Intelligence

Vercel's durable-harness Enables Automatic Crash Recovery for AI Agents

Vercel open-sources durable-harness, an adapter that adds durable execution to coding agents like Claude Code and Codex by logging every model and tool call to a persistent log, enabling automatic recovery after crashes with configurable replay strategies for safe and unsafe tools, flexible deployment from local files to Postgres, and multiple filesystem modes for different workloads.

AI agentsCrash RecoveryVercel
0 likes · 5 min read
Vercel's durable-harness Enables Automatic Crash Recovery for AI Agents
AliExpress Tech
AliExpress Tech
Oct 9, 2026 · Backend Development

Event-Sourced Reliable Execution Framework for Multi-Agent Video Generation

The article details a Java framework that uses event sourcing as the sole fact source, a deterministic rule table for control-plane decisions, and mechanisms for crash recovery, concurrency control, budget enforcement, compliance gating, and non-blocking human approvals to make long-running, costly multi-agent video pipelines reliable.

Crash RecoveryJava frameworkbudget enforcement
0 likes · 30 min read
Event-Sourced Reliable Execution Framework for Multi-Agent Video Generation
TonyBai
TonyBai
Oct 3, 2026 · Artificial Intelligence

Pi 1.0 & Pi Durable: Unkillable Agent Harness Adds MCP Support & Crash Recovery

The article analyzes Pi 1.0 and Pi Durable, a minimalist agent harness framework that now supports MCP via Codemode, introduces virtual model routing, and provides six durability primitives including crash recovery, session forking, and background compression for long-running, multi-user agent applications.

Agent HarnessCodemodeCrash Recovery
0 likes · 27 min read
Pi 1.0 & Pi Durable: Unkillable Agent Harness Adds MCP Support & Crash Recovery
Architect
Architect
Oct 1, 2026 · Artificial Intelligence

Pi vs DeepSeek Harness: Agent Loop Design for Continuation, Closure & Recovery

This article compares Pi and DeepSeek Harness agent loop architectures across four control points—input attribution, tool scheduling, closure permissions, and persistent evidence—revealing how each handles mid-task user constraints, parallel tool execution, token truncation, and crash recovery through distinct runtime contracts and durable extensions.

Agent ArchitectureCrash RecoveryDeepSeek Harness
0 likes · 20 min read
Pi vs DeepSeek Harness: Agent Loop Design for Continuation, Closure & Recovery
ITPUB
ITPUB
Sep 7, 2026 · Databases

InnoDB Checkpoint Internals: Sync vs Fuzzy, Crash Recovery Detection, and Four Failure Scenarios

This article explains InnoDB's checkpoint mechanism, contrasting synchronous and fuzzy checkpoints, detailing the pre-MySQL 8.0 fuzzy checkpoint implementation using flush lists and page cleaners, and describing two principles for detecting abnormal shutdowns plus four post-restart crash scenarios with their recovery requirements.

Crash RecoveryInnoDBLSN
0 likes · 11 min read
InnoDB Checkpoint Internals: Sync vs Fuzzy, Crash Recovery Detection, and Four Failure Scenarios
21CTO
21CTO
Sep 4, 2026 · Databases

ElephpantDB: Full SQL Database in One PHP File

ElephpantDB is an experimental SQL database implemented in a single PHP file, supporting CREATE TABLE, SELECT, UPDATE, DELETE, indexes, prepared statements, an append-only heap with crash recovery, hash indexes, and an optional HTTP JSON endpoint, running on PHP 8.3+.

Crash RecoveryElephpantDBHTTP API
0 likes · 5 min read
ElephpantDB: Full SQL Database in One PHP File
Radish, Keep Going!
Radish, Keep Going!
Aug 24, 2026 · Artificial Intelligence

PI's Agent Runtime v2: Crash Recovery as the First Constraint

PI's 3,446-line harness-v2.md redesigns the agent runtime around crash recovery as the primary constraint, using intent records with provisioned IDs, a four-layer session state, persisted retry counts, deferred writes to preserve provider KV cache, and exhaustive crash-point testing via manual drive mode.

Crash RecoveryKV cache preservationPi agent
0 likes · 27 min read
PI's Agent Runtime v2: Crash Recovery as the First Constraint
James' Growth Diary
James' Growth Diary
Jun 15, 2026 · Backend Development

How Slash Commands Are Routed in the Hermes TUI Gateway

The article explains the design of Hermes' terminal UI gateway, detailing why the TUI does not import the Agent directly, how JSON‑RPC over stdio or WebSocket enables local and remote modes, and how slash commands are processed through a two‑layer routing system with a dedicated _SlashWorker subprocess and a pure‑function crash‑recovery plan.

Crash RecoveryGatewayHermes
0 likes · 16 min read
How Slash Commands Are Routed in the Hermes TUI Gateway
Architect Chen
Architect Chen
May 4, 2026 · Databases

What’s the Difference Between MySQL Redo Log and Binlog? (Interview Insight)

The article explains that MySQL redo log operates at the InnoDB engine layer to ensure transaction durability and crash recovery, while binlog works at the server layer to record logical changes for replication, archiving, and point‑in‑time recovery, highlighting their distinct layers, purposes, content, and write mechanisms.

Crash RecoveryInnoDBMySQL
0 likes · 4 min read
What’s the Difference Between MySQL Redo Log and Binlog? (Interview Insight)
Programmer1970
Programmer1970
Nov 23, 2025 · Databases

MySQL Core Concepts Interview Q&A: 10 Essential Topics (Part 2)

This article provides detailed explanations of ten core MySQL topics—including InnoDB lock upgrades, redo log mechanics, MVCC version chains, tablespace types, page splitting, optimizer plan selection, crash recovery, binlog vs redo log, adaptive hash index, and memory management—along with practical tips for avoiding pitfalls and tuning performance.

Adaptive Hash IndexCrash RecoveryInnoDB
0 likes · 22 min read
MySQL Core Concepts Interview Q&A: 10 Essential Topics (Part 2)
Tencent Database Technology
Tencent Database Technology
Feb 28, 2023 · Databases

Understanding InnoDB Undo Segment States and MySQL XA Transaction Crash Recovery (MySQL 8.0.30)

This article explains how InnoDB uses undo segment states for crash‑safe recovery, details the XA transaction protocol, describes bugs in earlier MySQL versions, and shows how MySQL 8.0.30 introduces a new undo state and revised prepare order to make external XA transactions crash‑safe, including code examples and recovery steps.

Crash RecoveryInnoDBMySQL
0 likes · 11 min read
Understanding InnoDB Undo Segment States and MySQL XA Transaction Crash Recovery (MySQL 8.0.30)
ByteDance SYS Tech
ByteDance SYS Tech
Nov 23, 2022 · Operations

How Virtio-fs Achieves Crash Recovery for High‑Availability Secure Containers

This article explains the design of Virtio-fs, its architecture and high‑availability features, and details the crash‑recovery mechanism—including crash models, state preservation, supervisor coordination, request idempotence, downtime optimization, and hot upgrade/migration—implemented by ByteDance's STE team for secure container workloads.

Crash RecoveryFUSEKVM
0 likes · 16 min read
How Virtio-fs Achieves Crash Recovery for High‑Availability Secure Containers
Aikesheng Open Source Community
Aikesheng Open Source Community
Sep 6, 2022 · Databases

Understanding MySQL Crash Recovery and the Role of Redo Logs

This article explains how MySQL performs crash recovery by using Redo logs, doublewrite buffers, undo tablespace handling, transaction subsystem initialization, and the processing of active, prepared, and committed transactions to restore data pages and ensure consistency after an unexpected shutdown.

Crash RecoveryDoublewriteInnoDB
0 likes · 28 min read
Understanding MySQL Crash Recovery and the Role of Redo Logs
Alibaba Cloud Developer
Alibaba Cloud Developer
Jun 2, 2021 · Databases

How PolarDB Guarantees Transaction Atomicity: From WAL to Visibility

This article explains how PolarDB ensures transaction atomicity by analyzing ACID principles, detailing the shortcomings of simple Direct‑IO and Buffer‑IO, introducing write‑ahead logging, full‑page backup, checkpointing, visibility mechanisms, and distinguishing durability and atomicity points to achieve reliable crash recovery and consistent data visibility.

Crash RecoveryPolarDBWAL
0 likes · 30 min read
How PolarDB Guarantees Transaction Atomicity: From WAL to Visibility
Ops Development Stories
Ops Development Stories
Apr 5, 2021 · Fundamentals

Understanding ZAB: How ZooKeeper Guarantees Strong Consistency

This article explains the ZAB (ZooKeeper Atomic Broadcast) protocol, detailing its atomic broadcast mechanism, two‑phase commit style messaging, transaction IDs (ZXID), leader‑follower coordination, crash recovery principles, data synchronization, and the underlying ZXID design with illustrative code snippets.

Crash RecoveryDistributed ConsensusZAB
0 likes · 11 min read
Understanding ZAB: How ZooKeeper Guarantees Strong Consistency
Architect's Tech Stack
Architect's Tech Stack
Mar 19, 2019 · Fundamentals

Understanding ZAB: The Zookeeper Atomic Broadcast Protocol

This article explains the ZAB protocol—Zookeeper's atomic broadcast and crash‑recovery mechanism—detailing its design, message‑broadcast process, leader election, transaction ordering with ZXID, and how it ensures data consistency and availability in distributed systems.

ConsensusCrash RecoveryZAB
0 likes · 8 min read
Understanding ZAB: The Zookeeper Atomic Broadcast Protocol
ITPUB
ITPUB
Jun 4, 2017 · Databases

Why Oracle Performs Crash Recovery Before Rollback: Understanding Instance Recovery

This article explains Oracle instance recovery, detailing when it is needed, how checkpoints and SCNs are recorded during clean and abnormal shutdowns, and the step‑by‑step forward‑roll and rollback process performed by SMON to restore database consistency after a crash.

Crash RecoveryInstance RecoveryOracle
0 likes · 8 min read
Why Oracle Performs Crash Recovery Before Rollback: Understanding Instance Recovery