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 2018/07/26 15:42:58 UTC

[GitHub] pnowojski commented on issue #6431: [FLINK-9972][flip6] Handle debug memory logging in flip6

pnowojski commented on issue #6431: [FLINK-9972][flip6] Handle debug memory logging in flip6
URL: https://github.com/apache/flink/pull/6431#issuecomment-408141485
 
 
   I think this is still valuable, since it's a much simpler way to achieve this goal. While troubleshooting, asking a user to configure slf4j-reporter imo is asking a bit too much. 
   
   But maybe somewhere down the road we could drop `MemoryLogger` and add some shortcote code that would setup slf4j-reporter correctly when `taskmanager.debug.memory.log` is set to true?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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


With regards,
Apache Git Services