[
https://issues.apache.org/jira/browse/FLINK-9972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16563589#comment-16563589
]
ASF GitHub Bot commented on FLINK-9972:
---------------------------------------
pnowojski commented on issue #6431: [FLINK-9972][flip6] Handle debug memory
logging in flip6
URL: https://github.com/apache/flink/pull/6431#issuecomment-409204313
Yes, probably you are right that we should be able to replace it with
Slf4jReporter. I had a wrong impression that you need to manually specify which
metrics you want to dump. But lets investigate it as separate ticket in the
future.
----------------------------------------------------------------
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:
us...@infra.apache.org
> Debug memory logging not working
> ---------------------------------
>
> Key: FLINK-9972
> URL: https://issues.apache.org/jira/browse/FLINK-9972
> Project: Flink
> Issue Type: Bug
> Components: TaskManager
> Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0
> Reporter: Piotr Nowojski
> Assignee: Piotr Nowojski
> Priority: Critical
> Labels: pull-request-available
>
> It seems like with introduction of Flip6, debug memory logging is not being
> initialised anymore and following config properties are ignored:
> * `taskmanager.debug.memory.log`
> * `taskmanager.debug.memory.log-interval`
> after disabling flip6 it works just fine.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
