[
https://issues.apache.org/jira/browse/HDFS-15718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Brennan resolved HDFS-15718.
--------------------------------
Resolution: Later
Closing this. This change is part of a larger feature that we are not ready to
put up yet.
> 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: 40m
> 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-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
