Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
None
-
None
-
Reviewed
Description
The background replication queue initialization processes configured number of blocks at a time and releases the namesystem write lock. This was to let namenode start serving right after a standby to active transition or leaving safe mode. However, this does not allow others to run much if the lock fairness is set to "unfair" for the higher throughput.
I propose adding a delay between unlocking and locking in the async repl queue init thread.