[
https://issues.apache.org/jira/browse/FLINK-23564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17392258#comment-17392258
]
Yang Wang commented on FLINK-23564:
-----------------------------------
I used to propose a similar solution in this PR[1]. But other devs are quite
concerned about stream redirections[2].
[1].
https://github.com/apache/flink/commit/2c1df7529825b6a0af7e57d29febeade36a758b1#diff-d91a03b520137b4a6b44993a960eb4cd4a7e0a92eba9de8aa3863ece9217fa8f
[2]. https://github.com/apache/flink/pull/11839#pullrequestreview-399769862
> 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)
