You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2022/10/26 02:21:26 UTC
[GitHub] [pulsar] leizhiyuan opened a new issue, #18198: [Bug] locks leak in LockManagerImpl
leizhiyuan opened a new issue, #18198:
URL: https://github.com/apache/pulsar/issues/18198
### Search before asking
- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.
### Version
master
### Minimal reproduce step
review the code
### What did you expect to see?
cache was cleaned normally
### What did you see instead?
see the pic
### Anything else?
private void handleDataNotification(Notification n) {
if (n.getType() == NotificationType.Deleted) {
ResourceLockImpl<T> lock = locks.get(n.getPath());
if (lock != null) {
lock.lockWasInvalidated();
}
}
// just do this
cache.invalidate(n.getPath());
}
### Are you willing to submit a PR?
- [X] I'm willing to submit a PR!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar] leizhiyuan closed issue #18198: [Bug] cache leak in LockManagerImpl
Posted by GitBox <gi...@apache.org>.
leizhiyuan closed issue #18198: [Bug] cache leak in LockManagerImpl
URL: https://github.com/apache/pulsar/issues/18198
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org