Hi all! I would like to start a discussion of FLIP-390: Support System out and err to be redirected to LOG or discarded[1].
In various production environments, either cloud native or physical machines, the disk space that Flink TaskManager can use is limited. In general, the flink users shouldn't use the `System.out.println` in production, however this may happen when the number of Flink jobs and job developers is very large. Flink job may use System.out to output a large amount of data to the taskmanager.out file. This file will not roll, it will always increment. Eventually the upper limit of what the TM can be used for is reached. We can support System out and err to be redirected to LOG or discarded, the LOG can roll and won't increment forever. This feature is useful for SREs who maintain Flink environments, they can redirect System.out to LOG by default. Although the cause of this problem is that the user's code is not standardized, for SRE, pushing users to modify the code one by one is usually a very time-consuming operation. It's also useful for job stability where System.out is accidentally used. Looking forward to your feedback, thanks~ [1] https://cwiki.apache.org/confluence/x/4guZE Best, Rui
