[ https://issues.apache.org/jira/browse/FLINK-10002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610059#comment-16610059 ]
zhangxinyu commented on FLINK-10002: ------------------------------------ [~wind_ljy] Thanks for your suggestions. # We could use "SizeAndTimeBasedRollingPolicy" to split by size or time. I think batch jobs may also have a large mount of logs. As we know, if the mount of logs is too large, the log UI may crash, so we can split by size. # Yes, the current implementation wouldn't cache logs. I think if the log is rotated, the log wouldn't be changed, so we can cache them in blob server. > WebUI shows logs unfriendly, especially when the amount of logs is large > ------------------------------------------------------------------------ > > Key: FLINK-10002 > URL: https://issues.apache.org/jira/browse/FLINK-10002 > Project: Flink > Issue Type: Improvement > Components: Webfrontend > Reporter: zhangxinyu > Priority: Major > Fix For: 1.7.0 > > Attachments: image-2018-09-10-11-38-07-973.png > > > When a streaming job run for a long time, the amount of logs may be very > large. The current WebUI shows all content of logs. It will cost much time to > download logs from task managers. and the browser cannot display the logs. > Therefore, I suggest that Flink uses DailyRollingAppender to split logs by > default, and task manager provides an API that can get logs based on a > parameter of time interval. In this way WebUI can display logs based on time > interval. -- This message was sent by Atlassian JIRA (v7.6.3#76005)