[
https://issues.apache.org/jira/browse/FLINK-20713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot closed FLINK-20713.
----------------------------------
Resolution: Auto Closed
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so I have gone ahead and closed it. If you are still affected by this
or would like to raise the priority of this ticket please re-open, removing the
label "auto-closed" and raise the ticket priority accordingly.
> 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
> Priority: Minor
> Labels: auto-closed, pull-request-available
> 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].
> 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/standalone support stdout/stderr redirection。
> c) Provide the default log4J configuration.
>
> flinkonyarn.png
> !redirect.jpg!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
