Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
Reviewed
Description
This Jira proposes to replace the FsDatasetImpl object lock with a separate lock object. Doing so will make it easier to measure lock statistics like lock held time and warn about potential lock contention due to slow disk operations.
Right now we can use org.apache.hadoop.util.AutoCloseableLock. In the future we can also consider replacing the lock with a read-write lock.
Attachments
Attachments
Issue Links
- breaks
-
HDFS-10828 Fix usage of FsDatasetImpl object lock in ReplicaMap
- Resolved
-
HDFS-10773 BlockSender should not synchronize on the dataset object
- Resolved
-
HDFS-10830 FsDatasetImpl#removeVolumes crashes with IllegalMonitorStateException when vol being removed is in use
- Resolved
- is related to
-
HDFS-13359 DataXceiver hung due to the lock in FsDatasetImpl#getBlockInputStream
- Resolved
-
HDFS-9668 Optimize the locking in FsDatasetImpl
- Patch Available
- is required by
-
HDFS-10742 Measure lock time in FsDatasetImpl
- Resolved