Skip to content
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.

Sign up for GitHub

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

Jump to bottom

just like other hazelcast locks, include a provision to destroy the locks once they are used #8

Open
krishna81m opened this issue Jul 10, 2015 · 0 comments
Open

just like other hazelcast locks, include a provision to destroy the locks once they are used #8

krishna81m opened this issue Jul 10, 2015 · 0 comments

Comments

@krishna81m
Copy link

As you can see below, all the keys pile up in heap "after all read/write unlocks are executed". It would be nice, just like other hazelcast locks, include a provision to destroy the locks once they are used or even an auto expiry after a certain time?

not-clearing-entries-on-unlock

hazelcast-read-write-lock-allocations
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@krishna81m