ZanderXu commented on PR #4945:
URL: https://github.com/apache/hadoop/pull/4945#issuecomment-1263411206

   @MingXiangLi Sir, thanks for your review.
   
   > Case2: It's wrong, but not caused by this lock.
   
   About this case, I will create one new PR to fix it.
   
   > And can avoid conflict cause by volume/block pool remove or add.
   
   We can add one synchronized lock to `addBlockPool` and `shutdownBlockPool` 
as before to avoid the conflict caused by volume/blockPool remove or add. And 
this synchronized just lock volume/blockPool remove or add, so it will not 
block other operations, such as read or write from client. If ok, I will fix it 
in a new ticket with Case2 together.
   
   @Hexiaoqiao looking forward your good ideas. 


-- 
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]

Reply via email to