Replicated by design
Configurable ensemble, write and acknowledgement quorums, with placement controls for availability zones and resource groups.
Understand the quorumWOODPECKER · OPEN-SOURCE WAL
Ordered, durable logs built on object storage.
Deploy a replicated WAL service or embed the engine in your Go application.
Replicate, then acknowledge. The client writes to the selected quorum. Acknowledgement follows the configured durability policy; compaction uploads completed data to object storage.
ILLUSTRATIVE TOPOLOGY · THREE REPLICAS SHOWN
01 / THE FOUNDATION
Separate the WAL from your application. Use replication for the active write path and object storage for compacted segments.
Configurable ensemble, write and acknowledgement quorums, with placement controls for availability zones and resource groups.
Understand the quorumStage active writes on LogStore nodes. Compact completed segments into object storage, separating compute from long-term retention.
Follow the storage lifecycleInspect runtime health, trace slow operations and diagnose replica data with the wp CLI and documented recovery workflows.
Open the CLI handbook02 / ONE ENGINE, TWO WAYS TO RUN
Choose a dedicated LogStore service or an in-process library. Both use etcd for coordination and share the Woodpecker log API.
Move WAL processing into a replicated LogStore cluster. Manage log storage independently from application compute.
Run the log engine inside your Go application. Use the object-storage backend without a separate LogStore cluster.
03 / FROM SYMPTOM TO ACTION
Operations are part of the product. Start with cluster health, inspect the affected log and replicas, then follow a recovery procedure grounded in the evidence.
Browse the complete CLI handbook# 1. Check runtime health
$ wp cluster health
Cluster Health: YELLOW
active: 3 decommissioning: 0 unreachable: 0
- zero redundancy (active == N)
# 2. Inspect a log's local durable coverage
$ wp log scan orders --mode raw
SEGMENT STATE META LAST REACHES 7 Completed 99 49
# 3. Read through the affected replicas
$ wp segment probe orders 7
Compare each replica's served range and outcome.
# Decide the next step from the findings.
04 / RELEASED. AND MOVING FORWARD.
With service mode released, Woodpecker is in an ongoing release cycle. The next phase deepens the foundations of a mature cloud-native WAL service.
Broader failure testing, predictable recovery and safer lifecycle transitions.
Higher throughput, lower tail latency and more efficient resource use.
Clearer diagnosis, controlled repairs and practical maintenance workflows.
More useful metrics, traces and explanations of runtime behavior.
YOUR NEXT STEP
Start a cluster, connect your application, or explore the operational toolkit.