

i found dead lock here, do you have any option for me? version is 2.3.0
@ben-manes https://github.com/brettwooldridge/HikariCP/issues/835 and https://github.com/brettwooldridge/HikariCP/commit/f75b0896de6ca075e1b0d2f4b3c792cf39b77643#diff-0dac8ca2574085e5192a8188ca22d42e might be interesting.
looks like a non-issue in the latest Caffeine, I only see usages of yield in tests, @520CHINA please update, latest version is 2.6.2.
Yes, please upgrade.
The issue is that the executor can have all its threads busy and the maintenance task is scheduled on its work queue. This means that a back off won鈥檛 help, since there are no free threads to run it. By instead taking the lock and doing the work as a last resort, it fixes the problem and flushes the write buffer. It also increases write throughput by reducing context switches, more aggressively flushes the write buffer, and does not busy wait.
This was fixed in 2.3.1 (#90) so you can do a patch update if necessary. Since I do try to strictly abide by semver, a full upgrade would be ideal for any other bug fixes.
Sorry for any trouble caused, but thanks for checking in with us about the issue.