You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by GitBox <gi...@apache.org> on 2020/04/28 14:53:54 UTC

[GitHub] [hadoop-ozone] elek commented on pull request #809: HDDS-2576. Handle InterruptedException in OzoneManagerDoubleBuffer

elek commented on pull request #809:
URL: https://github.com/apache/hadoop-ozone/pull/809#issuecomment-620657607


   > However, I guess it would worth it just for homogeneity and to get rid of the sonar's bug.
   
   I am fine to get it for homogeneity, unless it cause problems in the behavior of the application. Marking a thread as interrupted during the normal operation can cause unexpected results (during unit test, or run).
   
   For me, it's hard to estimate the risk, and it seems to be unnecessary. Wouldn't be more safe to mark the violation in Sonar as false positive?


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

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org