Siyao Meng created HDDS-16451:
---------------------------------
Summary: Cross lock lost update of ContainerInfo sequenceId
(masked by report resend and writeLock)
Key: HDDS-16451
URL: https://issues.apache.org/jira/browse/HDDS-16451
Project: Apache Ozone
Issue Type: Bug
Reporter: Siyao Meng
h3. Finding
Cross-lock lost update of a shared ContainerInfo sequenceId (report path under
synchronized(containerInfo), Ratis-apply path under striped writeLock(id)) is a
real race but its harm is masked: for OPEN/QUASI_CLOSED the periodic report
resend re-raises the value via max(), and the durable/follower value is
serialized under writeLock so an in-memory clobber cannot corrupt it. Internal
invariant violation with downstream risk (an understated in-memory seqId
feeding a resurrection/close decision in a narrow window) but no consumer
observed the wrong outcome.
h3. Classification
* Verdict: MASKED
* Severity: Medium
* Source: Specula TLA+ model checking and confirmation debate, finding CR-4
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]
