sodonnel commented on pull request #3907: URL: https://github.com/apache/hadoop/pull/3907#issuecomment-1032457941
I am also concerned about yielding the lock in the middle of processing a storage. I would be interested to understand where the time is spend doing the block report processing inside the namenode, to see if we can improve the performance of the code and avoid yielding the lock. Have you tried reproducing this problem on a small otherwise idle cluster and attaching the async profiler to the namenode process to see where the code is taking time during block reporting? I think that analysis would be valuable before we change the locking, as there may be something which can be improved around the performance. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
