[
https://issues.apache.org/jira/browse/HDFS-13602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Shvachko updated HDFS-13602:
---------------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.7.7
2.8.5
3.0.4
2.9.2
3.1.1
3.2.0
2.10.0
Status: Resolved (was: Patch Available)
I just committed this. Looks like we had this in all versions. Backported down
to branch 2.7.
Thank you [~csun].
> Add checkOperation(WRITE) checks in FSNamesystem
> ------------------------------------------------
>
> Key: HDFS-13602
> URL: https://issues.apache.org/jira/browse/HDFS-13602
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: ha, namenode
> Reporter: Erik Krogen
> Assignee: Chao Sun
> Priority: Major
> Fix For: 2.10.0, 3.2.0, 3.1.1, 2.9.2, 3.0.4, 2.8.5, 2.7.7
>
> Attachments: HDFS-13602.000.patch, HDFS-13602.001.patch
>
>
> Similar to the work done in HDFS-4591 to avoid having to take a write lock
> before checking if an operation category is allowed, we can do the same for
> the write lock that is taken sometimes (when updating access time) within
> getBlockLocations.
> This is particularly useful when using the standby read feature (HDFS-12943),
> as it will be the case on an observer node that the operationCategory(READ)
> check succeeds but the operationCategory(WRITE) check fails. It would be
> ideal to fail this check _before_ acquiring the write lock.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
