Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Duplicate
-
None
-
None
-
None
-
None
Description
Right now the getContentSummary call on the namenode only holds the FSDirectory lock, but not the FSNamesystem lock. What we are seeing because of that is:
1) getContentSummary takes the read lock on FSDirectory
2) the write operation comes and takes a write lock on FSNamesystem and waits for getContentSummary to finish to get a write lock on FSDirectory
As a result other read operations can't be executed. Since getContentSummary can take a while to execute on large directories, the performance would be improved if we hold a readlock while doing that.
Attachments
Issue Links
- is duplicated by
-
HDFS-988 saveNamespace race can corrupt the edits log
- Closed