Siyao Meng created HDDS-16462:
---------------------------------
Summary: Recon full snapshot onto an earlier OM lineage plus crash
permanently serves stale derived data
Key: HDDS-16462
URL: https://issues.apache.org/jira/browse/HDDS-16462
Project: Apache Ozone
Issue Type: Bug
Reporter: Siyao Meng
h3. Finding
A full-snapshot swap onto an earlier OM lineage plus a crash before the async
reprocess becomes durable leaves derived tables permanently built against the
old OM lineage, because epoch-blind strict-less-than reconciliation judges the
stale task caught up; Recon REST/API/UI then serves rows the current OM lineage
does not contain, with no self-heal. Triggerable via the documented
delta-failure to full-snapshot fallback after an OM DR restore or re-bootstrap.
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: recon-om-sync
Guidance: campaigns/ozone-9fbf9ee/targets/023-recon-om-sync/.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
\
"recon-om-sync|apache/ozone|Java|Use the target-specific .prompt-extra.md"
{code}
Discovered under HDDS-16434 (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]
