Github user casidiablo commented on the issue:

    https://github.com/apache/flink/pull/5399
  
    The reason I proposed the change is that any unexpected behavior, even when 
you can recover from it, can be indicative of a potential bug/misconfiguration. 
INFO logs are by far noisier than errors, which means it is tough to identify 
problems unless you log them with ERROR (or at least WARN).
    
    I'd say we at least demote this to WARN. When one is analyzing logs, trying 
to find leads to current problems, it's common to filter out all INFO logs 
(otherwise it's mayhem); so anything that caused an exception to be thrown 
should be highlighted.


---

Reply via email to