Skip to content

Conversation

@shultseva
Copy link
Contributor

@shultseva shultseva commented Oct 20, 2025

The cleanup threshold property for the event journal.

Introduced here:
https://hazelcast.atlassian.net/browse/CTT-739
https://hazelcast.atlassian.net/browse/CTT-761

@shultseva shultseva requested a review from a team as a code owner October 20, 2025 11:16
@netlify
Copy link

netlify bot commented Oct 20, 2025

Deploy Preview for hardcore-allen-f5257d ready!

Name Link
🔨 Latest commit 7e15958
🔍 Latest deploy log https://app.netlify.com/projects/hardcore-allen-f5257d/deploys/68ff8f0d4bd20000082bf028
😎 Deploy Preview https://deploy-preview-1946--hardcore-allen-f5257d.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@shultseva shultseva changed the title New cluster property New cluster property - hazelcast.journal.cleanup.threshold Oct 20, 2025
@shultseva shultseva changed the title New cluster property - hazelcast.journal.cleanup.threshold New cluster property - hazelcast.journal.cleanup.threshold [CTT-761, CTT-739] Oct 20, 2025
Copy link
Contributor

@Rob-Hazelcast Rob-Hazelcast left a comment

Choose a reason for hiding this comment

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

Looks great, thanks for the quick turnaround

devOpsHazelcast pushed a commit to hazelcast/hazelcast that referenced this pull request Oct 26, 2025
jira - https://hazelcast.atlassian.net/browse/CTT-761

Additional cleanup for **cache** is now triggered before the add
operation.
Cleanup runs on both the primary replica and backups.
Cleanup starts only when the remaining capacity falls below a cleanup
threshold.

doc = hazelcast/hz-docs#1946
benchmark - https://github.com/hazelcast/internal-benchmarks/pull/67
Checklist:

- [x] Labels (`Type:`, `Source:`, `Module:`) and Milestone set
- [x] Label `Add to Release Notes` or `Not Release Notes content` set
- [x] Label `All Languages Should Check` set if making changes to the
Java client API and it may effect non-Java clients. Setting this label
will auto generate associated issues in all non-Java clients.
- [x] Architecture Design Record (ADR) reviewed and signed-off if this
PR represents a significant architectural change
- [x] Request reviewers if possible
- [x] New public APIs have `@Nonnull/@Nullable` annotations
- [x] New public APIs have `@since` tags in Javadoc
- [ ] Send backports/forwardports if fix needs to be applied to
past/future releases

GitOrigin-RevId: edb67ff4ad816187cb285ef7894b47c1b6032ed9
shultseva and others added 6 commits October 27, 2025 15:07
Co-authored-by: Krzysztof Jamróz <79092062+k-jamroz@users.noreply.github.com>
Co-authored-by: Krzysztof Jamróz <79092062+k-jamroz@users.noreply.github.com>
Co-authored-by: Krzysztof Jamróz <79092062+k-jamroz@users.noreply.github.com>
Co-authored-by: Krzysztof Jamróz <79092062+k-jamroz@users.noreply.github.com>
@shultseva shultseva requested a review from k-jamroz October 28, 2025 11:36
| 1.0
| float
| The cleanup threshold for the event journal, expressed as a fraction of its capacity (a value between 0.0 and 1.0).
When the remaining capacity falls below this threshold, a cleanup may be triggered during put operations to remove expired events (only if a xref:data-structures:event-journal.adoc#configuring-event-journal-ttl[time-to-live] for event journal is configured).
Copy link
Contributor

@k-jamroz k-jamroz Oct 28, 2025

Choose a reason for hiding this comment

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

during put operations

I am wondering (maybe nit-picking) if it is clear that we mean here journal/ringbuffer put operation and not IMap/ICache put operation

@shultseva shultseva merged commit 3920cb1 into hazelcast:main Oct 30, 2025
6 checks passed
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.

3 participants