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

Jim Brennan commented on HDFS-15718:
------------------------------------

[~ahussein] this change is a portion of a march larger feature that [~daryn] is 
working on. I don't think it makes sense to separate out this portion.  I 
propose we close this Jira as invalid.

 

> Optimize hdfs token op writeLock
> --------------------------------
>
>                 Key: HDFS-15718
>                 URL: https://issues.apache.org/jira/browse/HDFS-15718
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: hdfs, namenode
>            Reporter: Ahmed Hussein
>            Assignee: Ahmed Hussein
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> [~daryn] noticed that token operations are acquiring the fsn write lock. Like 
> lease renewal and token expiration, the read lock is sufficient because the 
> namesystem is not mutated.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to