ArchitectureA supervised JVM-class runtime — OLTP on seven engines, OLAP on three. AI-native, MCP-native, observable as plain SQL.Read the architecture
Está viendo la edición Perú. Está viendo la edición Colombia. You're viewing the Pakistan edition. Cambiar a la edición global →Cambiar a la edición global →Switch to the global edition →
Runtime and operationsProduct Release1 min read

Operating the capture server: pause a table, resume it, keep it up with systemd

A table can be paused and resumed from the command line or the REST API so DDL runs without stopping capture. A health endpoint answers 200 or 503, and a systemd unit restarts the server.

The capture server of 2025 worked. Operating it meant stopping it. This release adds the controls an operator needs between the start and the stop.

Controls

  • Pause one table A command or a REST call pauses capture on a table so an ALTER TABLE can run, and resumes it after. Informix pauses per table through its capture API; PostgreSQL pauses the whole database, which the server states rather than hides.
  • Health An unauthenticated endpoint returns capture state, server errors and scope count, with 200 when healthy and 503 otherwise.
  • Kept up A systemd unit with automatic restart and journal logging, install and uninstall scripts, a manager script for start, stop and restart, and a switch for full-row logging.

Proven

  • The watch set from the engine Replicated tables are read from the Informix system catalog, so the server watches what the engine actually replicates. Production configurations are validated by a test, and pause and resume have four container tests on Informix.

The node later learned to capture without the server. For estates that keep it, this is how it is run.

On the platformOperationsPlatform

All posts