Siyao Meng created HDDS-16454:
---------------------------------
Summary: New SCM leader with apply lagging commit drops container
reports as CONTAINER_NOT_FOUND
Key: HDDS-16454
URL: https://issues.apache.org/jira/browse/HDDS-16454
Project: Apache Ozone
Issue Type: Bug
Reporter: Siyao Meng
h3. Finding
The new-leader branch starts the datanode server with applied index below
committed index, so reports for committed-but-unapplied containers are dropped
as CONTAINER_NOT_FOUND, leaving SCM's in-memory replica-location accounting
incomplete; triggerable when leadership moves to a node whose apply lags
commit. Masked because the default WARN action never deletes the physical
replica, the NodeManager node-to-container map is retained, and
replication-manager consumers are gated on isLeaderReady and safe-mode exit, so
only self-correcting RM churn could surface in the report-interval window.
h3. Classification
* Verdict: MASKED
* Severity: Medium
* 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-follower-catchup
Guidance:
campaigns/ozone-9fbf9ee/targets/019-scm-follower-catchup/.prompt-extra.md
{noformat}
{code:none}
specula run --agent=claude-code --effort=high --keep-original --max-parallel=2 \
--enable-reviews --confirm-debate --tlc-memory-limit=28G --tlc-worker-limit=8
\
"scm-follower-catchup|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]
