Skip to content

13.7.2.1

Pre-release
Pre-release

Choose a tag to compare

@kderme kderme released this 17 Jun 13:47
· 0 commits to master since this release
13.7.2.1
db8cdf6

DB Sync 13.7.2.1

DB Sync 13.7.2.1 is a redesign of the epoch table. The legacy in-memory cache that maintained it (and caused several rollup-corruption bugs over the past releases) is removed; the epoch interface is now a view over an append-only epoch_finalized table and a live epoch_current view. Consumer-visible reads are unchanged.

This release also fixes a long-standing pool_relay.port overflow.

Upgrading

Upgrading from 13.7.1.X runs two startup migrations:

Upgrading from 13.7.0.X additionally runs the epoch fix migration shipped with 13.7.1.0 (migration-2-0048-20260520.sql) before the migrations above.

Snapshots

The release is compatible with both 13.7 and 13.6 DB snapshots:

Network Link
Mainnet 13.7 https://update-cardano-mainnet.iohk.io/cardano-db-sync/index.html#13.7/
Mainnet 13.6 https://update-cardano-mainnet.iohk.io/cardano-db-sync/index.html#13.6/

Changelog

https://github.com/IntersectMBO/cardano-db-sync/blob/13.7.2.1/CHANGELOG.md#13721

LSM (experimental)

  • Enable by setting "ledger_backend": "lsm" in the db-sync config — see config docs.
  • Snapshots can be converted between InMemory and LSM with snapshot-converter — see snapshot docs.
    The compatible snapshot-converter is shipped with node-11.0.1.
  • --bootstrap-tx-out is not supported with LSM.

Notes

When running db-sync, enable only the data you actually need. This is configured in the db-sync config file — see config docs.

Because epoch is now a view that computes the current (non-finalized) epoch on the fly, queries against it may be slightly slower on the order of ~500ms on mainnet. If you don't need the latest in-progress epoch, query the underlying epoch_finalized table directly: it is faster but does not include the latest epoch.

Platforms

Known issues

  • duplicate off-chain vote metadata child rows #2137
  • When using the LSM storage backend, db-sync cannot read blocks with more than 4096 items due to a bug in blockio-uring. This issue already has a fix that will be included into the next release.
  • When using the LSM storage backend, db-sync could crash due to how ghc handles system threads. This only happens on resource-constrained devices such as the Raspberry Pi. The fix will be shipped in the next release.
  • When using the LSM storage backend, the CPU idle time is reported as iowait. This is not a performance or correctness issue, but it may be confusing. The fix will be shipped in the next release.

Sign-off

Role Approval
Technical Lead 🟢
Intersect TSC
Intersect Product Committee
Test Engineer 🟢
Site Reliability Engineer