mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-11-10 22:50:59 +08:00
binwiederhier
b0ae219486
Makes clustering usable: experimental-cluster-listen is accepted now and the startup guard is gone. The server holds a cluster, constructs it with the callbacks it supplies (so the cluster package never imports the server), and serves the peer API on a dedicated private listener that the public listeners never expose. dispatch, the one choke point every publish path goes through, hands each message to the cluster before delivering locally. deliverFromBus publishes an inbound peer message to the local topic and nothing else: the origin already ran Firebase, email, web push and upstream, so a peer never re-fires them or re-relays. /v1/health answers 503 once this node's registration has gone stale, so a load balancer can pull it, and the cluster calls closeLocalSubscribers when this node is isolated but a peer is healthy, so those clients reconnect elsewhere. Two jobs become leader-only, checked per tick to survive failover. The Firebase keepaliver has to be: one keepalive wakes every subscribed phone. The delayed sender does not, and the comment says so, since the claim in the message cache is what makes that safe; the gate only keeps the work on one node. What a cluster does not do yet, each waiting for its own piece: recover a dropped fan-out batch, enforce rate limits and quotas across nodes, share per-topic state (UnifiedPush billing, the Matrix pushkey decision), replay unflushed messages to a reconnecting subscriber, or relay subscriber cancels. Hence experimental-.