- 
                Notifications
    You must be signed in to change notification settings 
- Fork 107
New cluster property - hazelcast.journal.cleanup.threshold [CTT-761, CTT-739] #1946
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| ✅ Deploy Preview for hardcore-allen-f5257d ready!
 To edit notification comments on pull requests, go to your Netlify project configuration. | 
There was a problem hiding this 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
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
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>
| | 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). | 
There was a problem hiding this comment.
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
The cleanup threshold property for the event journal.
Introduced here:
https://hazelcast.atlassian.net/browse/CTT-739
https://hazelcast.atlassian.net/browse/CTT-761