We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Expected Behavior If you're okay I'm working on it and I'm trying to post a PR.
Current Behavior now If you use a lot of different keys Currently, you have to call expireUnusedOlderThan() manually.
expireUnusedOlderThan()
after change Developers can use it without manually invoking it. If you do not want local caching, you can also disable caching by setting capacity.
capacity
Context
Similar to an issue before, I'd like to contribute. #3655
The text was updated successfully, but these errors were encountered:
GH-3672: Clean up Jdbc & ZK LockRegistry caches
db61102
Fixes #3672 * Clean up `JdbcLockRegistry`, `ZookeeperLockRegistry` cache automatically * setCapacity(int capacity) to cacheCapacity(int capacity) * field rename `capacity`to `cacheCapacity`, add static
Successfully merging a pull request may close this issue.
Expected Behavior
If you're okay
I'm working on it and I'm trying to post a PR.
Current Behavior
now
If you use a lot of different keys
Currently, you have to call
expireUnusedOlderThan()
manually.after change
Developers can use it without manually invoking it.
If you do not want local caching, you can also disable caching by setting
capacity
.Context
Similar to an issue before, I'd like to contribute.
#3655
The text was updated successfully, but these errors were encountered: