Siyao Meng created HDDS-16438:
---------------------------------

             Summary: FSO lifecycle scan can skip an unscanned directory's 
expired keys after a mid scan crash
                 Key: HDDS-16438
                 URL: https://issues.apache.org/jira/browse/HDDS-16438
             Project: Apache Ozone
          Issue Type: Bug
            Reporter: Siyao Meng


h3. Finding
Cache-first unordered enumeration breaks canSkipDir's descending-order premise, 
so on crash/resume an unscanned FSO directory is skipped and its expired keys 
are not collected; the demonstrated external effect (expired data left 
uncollected past its lifecycle policy) is currently masked by the 
next-generation fresh rescan, and absent that rescan the skip would persist and 
recur under repeated faults. Reachable through the FSO lifecycle scan on any 
bucket with a concurrent mkdir in the partial cache during a mid-scan crash. 
MASKED: classified by the consequence the defect would expose if the rescan 
mask were absent.

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

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