Siyao Meng created HDDS-16448:
---------------------------------

             Summary: A CLOSED container's sequenceId is silently bumped by a 
higher BCSID report, stranding quorum correct replicas
                 Key: HDDS-16448
                 URL: https://issues.apache.org/jira/browse/HDDS-16448
             Project: Apache Ozone
          Issue Type: Bug
            Reporter: Siyao Meng


h3. Finding
Internal invariant violation (a CLOSED container's immutable sequenceId is 
silently bumped by a healthy higher-BCSID replica report) that demonstrably 
propagates to external effect: RatisContainerReplicaCount reclassifies 
quorum-correct QUASI_CLOSED replicas as unhealthy (healthy count 3 to 1), so a 
fully-replicated CLOSED container is treated as under-replicated and 
MismatchedReplicasHandler strands those replicas. Triggerable Level 0 through 
the real ContainerReportHandler.onMessage path with an ordinary DN report; the 
bump is monotonic with no downstream self-heal.

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

h3. Reproduce
{noformat}
Ozone commit: 9fbf9ee0cb1bd2f5f5d437b6719ebbe5309351fb
Specula:      v1.1.0 (commit c6aa3dfa)
Target:       scm-container-lifecycle
Guidance:     
campaigns/ozone-9fbf9ee/targets/015-scm-container-lifecycle/.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-container-lifecycle|apache/ozone|Java|Use the target-specific 
.prompt-extra.md"
{code}
Discovered under HDDS-16431 (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