Skip to content

HDDS-16420. Use partial cache for OmLifecycleConfiguration and OmLifecycleScanState table - #11241

Open
ChenSammi wants to merge 3 commits into
apache:masterfrom
ChenSammi:HDDS-16420
Open

ChenSammi wants to merge 3 commits into
apache:masterfrom
ChenSammi:HDDS-16420

Conversation

@ChenSammi

Copy link
Copy Markdown
Contributor

What changes were proposed in this pull request?

Use partial cache for OmLifecycleConfiguration and OmLifecycleScanState table, instead of full cache, since the bucket lifecycle configuration evaluation happens by default once a day.

What is the link to the Apache JIRA

https://issues.apache.org/jira/browse/HDDS-16420

How was this patch tested?

Copilot AI lite review requested due to automatic review settings September 15, 2026 05:17

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

Partial caching can cause persisted lifecycle policies to be skipped after restart or cache eviction.

Get a fresh assessment by requesting another Copilot review.

Pull request overview

This PR switches lifecycle configuration and scan-state tables to partial caching to reduce OM memory usage.

Changes:

  • Uses partial-cache initialization for both lifecycle tables.
  • Retains persisted lifecycle metadata in RocksDB.
File summaries
File Summary
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/OmMetadataManagerImpl.java Changes lifecycle table caching; lifecycle listing still uses cache-only iteration, creating a critical unresolved issue.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 1
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants