[
https://issues.apache.org/jira/browse/HDFS-15718?focusedWorklogId=521776&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-521776
]
ASF GitHub Bot logged work on HDFS-15718:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 08/Dec/20 17:28
Start Date: 08/Dec/20 17:28
Worklog Time Spent: 10m
Work Description: amahussein opened a new pull request #2531:
URL: https://github.com/apache/hadoop/pull/2531
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.
@daryn-sharp suggested to improve performance by substituting writeLock with
readLock.
CC: @jbrennan333
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 521776)
Remaining Estimate: 0h
Time Spent: 10m
> 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
> Time Spent: 10m
> 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: [email protected]
For additional commands, e-mail: [email protected]
