[ 
https://issues.apache.org/jira/browse/HDFS-17603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18021622#comment-18021622
 ] 

ASF GitHub Bot commented on HDFS-17603:
---------------------------------------

github-actions[bot] commented on PR #7054:
URL: https://github.com/apache/hadoop/pull/7054#issuecomment-3315390308

   We're closing this stale PR because it has been open for 100 days with no 
activity. This isn't a judgement on the merit of the PR in any way. It's just a 
way of keeping the PR queue manageable.
   If you feel like this was a mistake, or you would like to continue working 
on it, please feel free to re-open it and ask for a committer to remove the 
stale tag and review again.
   Thanks all for your contribution.




> [FGL] Abstract a LockManager to manage locks 
> ---------------------------------------------
>
>                 Key: HDFS-17603
>                 URL: https://issues.apache.org/jira/browse/HDFS-17603
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: ZanderXu
>            Assignee: Felix N
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: image-2024-08-14-17-17-28-792.png
>
>
> Abstract a LockManager to manage locks. 
> Some requirements for this LockManager:
>  * Cached a fixed number lock instances, such as: 1000
>  * Assign a Lock instance to a key and keep this mapping until the key 
> released this instance
>  * This LockManager needs a high performance, such as: QPS 1000w
>  
> Some implementations that we can refer to:
>  * alluxio.collections.LockPool in Alluxio
>  * Implementation in MEITUAN 
> !image-2024-08-14-17-17-28-792.png|width=205,height=196!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to