fix(controller): bug-1433 async-thread fdatasync block + bug-1434 committed_lsn CAS race
bug-1433: raft_cb_become_leader runs synchronously off peer_ctrl_dispatch_to_pool, which hardcodes VTASK_LIVENESS for every inbound peer-control packet including vote replies. The bug-1431 round-2 fix (flusher_flush_once force-flush in persist_promotion_advance_committed) was reachable from that never-blocks task class -- same bug family as bug-1198. Removed the force-flush; round-3 (durable-capped only) plus the already-shipped bug-1432 immediate-first-heartbeat fix close the visibility-latency gap non-blockingly. TRACKED RESIDUAL: persist_apply_pump_run_sync is still reachable on the same VTASK_LIVENESS path and does bounded pread() -- lower risk (page-cache-hot) but strictly still blocking I/O; not safe to remove outright (reopens bug-1043-family job loss), needs its own follow-up (reclassify peer_ctrl_classify's winning-vote-reply case or dispatch promotion tail onto a fresh VTASK_LIVE_BLOCK vtask). bug-1434: persist_promotion_advance_committed and ha_standby_advance_committed_and_apply raced on persist_t.committed_lsn via an unlocked load-then-conditional-store during the promotion window (before ha->role flips to CTRL_PRIMARY) -- a losing racer could regress committed_lsn. Added persist_committed_lsn_advance_atomic (CAS retry loop, lock-free) and routed both call sites through it. Validated: 19/19 unit test suites, 6-round chaotic soak (0 loss/divergence) + 6-round sequential+leadership-coverage soak, both PASS. Also folds in raft-apply-decoupling and raft-ha-core-safety validate-impl phase bumps to "implemented" and clears config-upgrade-snapshot's now-satisfied entity-bearing-snapshots block.
This commit is contained in:
parent
ea0ac81c92
commit
40f510fb14
25 changed files with 1617 additions and 226 deletions
|
|
@ -1172,6 +1172,18 @@ int iomgr_init(iomgr_t* iomgr)
|
|||
* any socket I/O, so this protects controller, worker, and scheduler. */
|
||||
signal(SIGPIPE, SIG_IGN);
|
||||
|
||||
/* bug-1406: establish every iomgr_t invariant here rather than assuming
|
||||
* the caller already zeroed the struct (do_endpoint_init follows this
|
||||
* same fully-explicit pattern for endpoint_t, a few lines above in this
|
||||
* file). Every production caller embeds iomgr_t inside a calloc'd/static
|
||||
* context struct, which previously masked this gap, but a caller that
|
||||
* stack-allocates an iomgr_t without a memset (test_ha_vep_teardown.c,
|
||||
* 4 call sites) left ssl_ctx as garbage; iomgr_fini's `!= NULL` guard then
|
||||
* passed on that garbage pointer and SSL_CTX_free() segfaulted on a wild
|
||||
* address. */
|
||||
iomgr->ssl_ctx = NULL;
|
||||
iomgr->worker = 0;
|
||||
|
||||
mylock_init(&(iomgr->lock));
|
||||
iomgr->epoll_fd = epoll_create1(0);
|
||||
if (iomgr->epoll_fd < 0) {
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue