Siyao Meng created HDDS-16452:
---------------------------------

             Summary: Inter SCM checkpoint served during an apply window ships 
data ahead of the durable index, diverging replicas
                 Key: HDDS-16452
                 URL: https://issues.apache.org/jira/browse/HDDS-16452
             Project: Apache Ozone
          Issue Type: Bug
            Reporter: Siyao Meng


h3. Finding
A checkpoint served by InterSCMGrpcService.download during an apply window 
ships data at index i under stale durable index i-1; a follower installs it and 
durably holds data ahead of its recorded index (CheckpointConsistent violated 
across replicas), then re-applies the entry on catch-up. Reproduced through the 
real concurrent apply/download APIs on a real store. For non-idempotent SCM 
transactions (e.g. deleted-block accounting, corroborated by a separate tracked 
issue) this diverges across SCM replicas with no automatic recovery; idempotent 
transactions self-heal via replay.

h3. Classification
* Verdict: REPRODUCED
* Severity: Critical
* Source: Specula TLA+ model checking and confirmation debate, finding MC-2

h3. Reproduce
{noformat}
Ozone commit: 9fbf9ee0cb1bd2f5f5d437b6719ebbe5309351fb
Specula:      v1.1.0 (commit c6aa3dfa)
Target:       scm-ha-tx-buffer
Guidance:     
campaigns/ozone-9fbf9ee/targets/018-scm-ha-tx-buffer/.prompt-extra.md
{noformat}
{code:none}
specula run --agent=claude-code --effort=medium --keep-original 
--max-parallel=2 \
  --enable-reviews --confirm-debate --tlc-memory-limit=28G --tlc-worker-limit=8 
\
  "scm-ha-tx-buffer|apache/ozone|Java|Use the target-specific .prompt-extra.md"
{code}
Discovered under HDDS-16432 (Specula TLA+ verification effort). The TLA+ 
specification, counterexample, and confirmation debate live in the Specula run 
artifacts.

Generated with Specula (Claude Opus 4.8).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to