[ 
https://issues.apache.org/jira/browse/HDDS-3118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Doroszlai updated HDDS-3118:
-----------------------------------
    Attachment: repro.patch
                repro.log

> 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
>            Priority: Major
>         Attachments: repro.log, repro.patch
>
>
> {{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: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org

Reply via email to