[
https://issues.apache.org/jira/browse/HDDS-3118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham updated HDDS-3118:
-------------------------------------
Fix Version/s: (was: 0.6.0)
0.5.0
> Possible deadlock in LockManager
> --------------------------------
>
> Key: HDDS-3118
> URL: https://issues.apache.org/jira/browse/HDDS-3118
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Attila Doroszlai
> Assignee: Bharat Viswanadham
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 0.5.0
>
> Attachments: repro.log, repro.patch
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> {{LockManager}} has a possible deadlock.
> # Number of locks is limited by using a {{GenericObjectPool}}. If N locks
> are already acquired, new requestors need to wait. This wait in
> {{getLockForLocking}} happens in a callback executed from
> {{ConcurrentHashMap#compute}} while holding a lock on a map entry.
> # While releasing a lock, {{decrementActiveLockCount}} implicitly requires a
> lock on an entry in {{ConcurrentHashMap}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
