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/06/02 09:42:09 UTC

[GitHub] [hadoop-ozone] elek commented on pull request #1006: HDDS-3699.Change write chunk failure logging level to INFO in BlockOutputStream.

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


   Thanks to open this issue @sadanand48. Unfortunately I don't have the context? (How did you notice this? What was the problem? How can I reproduce it?).
   
   Therefore, I have a few questions to understand this patch:  
   
   Why don't we use `ERROR`, why do we need `INFO`?
   
   What is the expected number of log messages in case of any error? (Let's say disk is not writable). Is it possible to a lot of INFO message?
   
   The exception seems to be propagated. Is it logged on higher level?
   


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