hubcio opened a new pull request, #4387: URL: https://github.com/apache/iggy/pull/4387
Lost replies and capacity eviction could erase retry evidence and permit duplicate mutations after promotion or restart. Persist original results by session, group and request identity. Replay the first receipt even when a retry changes its payload, while preserving principal, session and client-operation guards. Protect committed capacity and publish receipt checkpoints before reclaiming their WAL. Refuse recovery when protection is absent or corrupt. Bind connections using client-owned proof, retain logical sessions across reconnects, renew leases only on authenticated activity, and retire protection across every allocated group before finalization. Preserve uncertainty when a later attempt is refused. Replay the exact encoded request after same-session resume. Refused expired sessions can log in again without replaying an ambiguous write under a new identity. Keep HTTP attachments invalidatable and drain bounded retirement sweeps between heartbeat reports. Retain attachments through materialization and keep awaited HTTP mutations behind the existing session gate. Restore recovered receipts before admission while allowing live pipeline-backed commits. Allow intact empty WALs to elect, fence missing history before replacement WAL creation, and compare bootstrap revisions in the same domain. Introduce protocol 0.11, mandatory storage admission and exact peer build checks. Require explicit fresh-cluster initialization and Persisted durability for explicit writes without changing defaults. Align Go, Java, C# and Node login proofs and shared binding frames. Cover changed-payload retries, reply loss, crash recovery and reclamation, corruption, capacity pressure, lifecycle fences and transport retries. Document first-receipt integrity stamps and stable binding epochs. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
