You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "muzimusi (Jira)" <ji...@apache.org> on 2020/12/22 07:45:00 UTC

[jira] [Created] (FLINK-20713) out/err file support rolling

muzimusi created FLINK-20713:
--------------------------------

             Summary: out/err file support rolling
                 Key: FLINK-20713
                 URL: https://issues.apache.org/jira/browse/FLINK-20713
             Project: Flink
          Issue Type: New Feature
          Components: API / Core, Runtime / Configuration
            Reporter: muzimusi
         Attachments: redirect.jpg

It is meaningful for out / err files to support scrolling. In particular, when you have to use stdout , writing out files continuously will eventually fill the disk. Similarly, err files will finally fill the disk when the job is keep rebooting with errors.


Recently, I saw some people asking for 'taskmanager.out rolling' in the [community email|[http://apache-flink.147419.n8.nabble.com/taskmanager-out-td9084.html|https://mail.google.com/mail/u/0/#search/label%3Aflink-zh+out/FMfcgxwKjnRnHpLBvQpJHqnBDZFhzDWS]]. We happened to have done this, hoping to help those in need.


The following is our implementation:
    a) Redirect stdout/stderr to logger .
    b) Flinkonyarn/Flinkonk8s already supports stdout/stderr redirection。
    c) Already provide the default log4J configuration.

!redirect.jpg!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)