Github user dkesler commented on the pull request:
https://github.com/apache/curator/pull/67#issuecomment-75567814
@cammckenzie The problem with requiring passing the lock instance to the
reaper to get the lock schema is that you can end up leaking locks. If the app
that took the lock doesn't successfully clean it up then other processes won't
know the schema of that particular lock instance since they need an instance of
the lock in order to clean it up.
Not entirely sure if it's a huge concern, but I thought I'd point it out
since I don't have insight as to possible future lock incarnations.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
