github Galxe/gravity-sdk v1.7.2
Gravity v1.7.2

latest releases: v1.10.0, v1.9.3, v1.9.2...
3 months ago

Gravity v1.7.2

Release: v1.7.2

Full Changelog: v1.7.1...v1.7.2

Related pinned components:

  • gravity-reth: rev 1aec7b75 — unchanged from v1.7.1.

A single-PR log-noise patch release. Pure log-level change, no behavioural change, no greth bump.

What's Changed

  • chore(consensus): downgrade hot-path per-round logs from info to debug by @Richard1048576 in #756

    • On the sub-second AptosBFT mainnet (~4–5 blocks/s) the consensus log floods at INFO: measured ~370 lines/s ≈ ~18.5 GB/day on a live mainnet validator. The bytes are dominated by per-message / per-round chatter and full certificate Debug dumps that carry no operational value at INFO. This drives node disk pressure and (where shipped) Cloud Logging cost.
    • Downgrades 10 hot-path log points info! → debug!. Measured impact on a 114 MB consensus-log sample: these 10 account for ~78% of consensus-log bytes → the consensus log drops to ~22% of current (~18.5 → ~4 GB/day).
    file log share of bytes
    epoch_manager.rs "consensus message peer {} msg {}" (full Debug; msg {:?} expands SyncInfo/Vote certs into the giant hqc: / hcc: QuorumCert + LedgerInfo blobs) ~62%
    block_storage/block_store.rs "insert qc {}" (full QuorumCert Display per block) ~4%
    pipeline/buffer_manager.rs "Receive commit vote …" ~7%
    pipeline/buffer_manager.rs "Advance execution root …" / "Advance signing root …" ~2.5%
    round_manager.rs "Local state {} … remote state {}" (SyncInfo dump) per-sync
    block_storage/sync_manager.rs "Fetching {} blocks, retry …" per-retry
    epoch_manager.rs "advancing block sync from peer …" catch-up
    liveness/round_state.rs "Processing certificates With SyncInfo" per round
    quorum_store/proof_manager.rs "QS: got clean request …" per QS req

    Operational signals stay at INFO: NewRound, block commits, epoch changes, and all warn! / error! (stale proposals, long waits, etc.). 10 lines, 7 files, no logic or signature changes. Follow-up (separate PR): reth-side per-block execution logs (reth.log, ~21 lines/block) live in gravity-reth + crates/block-buffer-manager.

Don't miss a new gravity-sdk release

NewReleases is sending notifications on new releases.