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

Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2021/01/04 17:39:45 UTC

[GitHub] [flink] rkhachatryan commented on pull request #14526: [FLINK-14814][WebUI] Highlight back pressured and busy nodes in the WebUI

rkhachatryan commented on pull request #14526:
URL: https://github.com/apache/flink/pull/14526#issuecomment-754113690


   Thanks for the update and clarification
   
   > Boxes are red until the first update of metric views. Until then, idleTime and backPressuredTime are zero, so by definition busyTime is 1000ms/s.
   
   I meant the metrics are just un-initialized (on JM) and that's not backpressure yet (I'm also fine with the current approach).
   
   > For sources, Busy time is always NaN%
   > That's by design
   
   Should we hide it then? Or at least show as `N/A`? `NaN` popping up in the UI usually means programmer error.
   
   > "Busy (max)" label - this shounds to me like max in time, not across subtasks
   > How would you rename this label?
   
   Busy (max across subtasks)? Or maybe add such a tooltip?


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