[ https://issues.apache.org/jira/browse/FLINK-23564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17393778#comment-17393778 ]
zlzhang0122 commented on FLINK-23564: ------------------------------------- [~wangyang0918] Maybe using log4j2-iostreams is a better choice to implemention, but it doesn't flush the buffer and would cause OutOfMemory error when using print, println didn't have this problem. I can't solve it and my implemention is mostly like yours. So far I didn't find any problem what other devs are concerned about. > Make taskmanager.out and taskmanager.err rollable > ------------------------------------------------- > > Key: FLINK-23564 > URL: https://issues.apache.org/jira/browse/FLINK-23564 > Project: Flink > Issue Type: Improvement > Affects Versions: 1.13.1 > Reporter: zlzhang0122 > Priority: Major > Fix For: 1.14.0 > > > Now users can use > System.out.print/System.out.println/System.err.print/System.err.println/e.printStackTrace > to taskmanager.out and taskmanager.err as much as they want and this may use > large space of disk cause the disk problem and influence the checkpoint of > the flink and even the stability of the flink or other application on the > same node. I proposed that we can make the taskmanager.out and > taskmanager.err rollable just like taskmanager.log.By doing this, the disk > consume of the taskmanager.out and taskmanager.err can be control. -- This message was sent by Atlassian Jira (v8.3.4#803005)