forked from lei.chen/myxce
obs(ha-term-safety): promote committed_lsn advance to INFO + harness polls authoritative commit signal
The commit-engine committed_lsn advance was TRACE-only; promoted to INFO (fires only
on a real advance, not noisy) so operators/tests can observe the authoritative primary
committed watermark. The clean-failover harness now polls this 'commit: committed_lsn
N -> M' line (not the lagging ha_process_standby_state heartbeat) with generous catch-up
headroom.
This made the live RED->GREEN visible: with Option A, committed_lsn reaches 5 on a
stable cluster ('jobs committed on a majority (committed_lsn=5 >= 5)') even via catch-up
delivery — the commit-stall is fixed.
This commit is contained in:
parent
83fbed2370
commit
9e5e293605
2 changed files with 18 additions and 8 deletions
|
|
@ -181,8 +181,13 @@ static void commit_advance_locked(commit_engine_t* ce)
|
|||
#endif
|
||||
|
||||
atomic_store(&ce->p->committed_lsn, cand);
|
||||
TRACE("commit: committed_lsn %lu -> %lu (n_peers=%d)", cur, cand,
|
||||
ce->n_peers);
|
||||
/* INFO (not TRACE): the authoritative primary committed_lsn advance. Fires
|
||||
* only on a real advance (monotonic guard above), so it is not noisy, and it
|
||||
* is the canonical operator/test signal for the committed watermark — the
|
||||
* standby-reported committed_lsn in ha_process_standby_state heartbeats lags
|
||||
* and only logs on the one-time converged transition. */
|
||||
INFO("commit: committed_lsn %lu -> %lu (n_peers=%d)", cur, cand,
|
||||
ce->n_peers);
|
||||
pthread_cond_broadcast(&ce->cond);
|
||||
}
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue