[ 
https://issues.apache.org/jira/browse/FLINK-13987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

lining updated FLINK-13987:
---------------------------
    Description: 
As log files becoming more large, current log api often blocks or don't work.

It's unfriendly for user. As application runs on jvm, sometime user need see 
log of gc.

Above all, we need new apis:
 * /taskmanagers/taskmanagerid/logs -> list all log file
 * /taskmanagers/taskmanagerid/logs/:filename?start=[start]&count=[count]
 * /jobmanager/logs -> list all log file
 * /jobmanager/logs/:filename?start=[start]&count=[count]

  was:
As log files becoming more large, current log api often blocks or don't work. 
It's unfriendly for user. As application runs on jvm, sometime user need see 
log of gc. Above all, we need new api.
 * /taskmanagers/taskmanagerid/logs -> list all log file
 * /taskmanagers/taskmanagerid/logs/:filename?start=[start]&count=[count]
 * /jobmanager/logs -> list all log file
 * /jobmanager/logs/:filename?start=[start]&count=[count]


> add new logs api, see more log files and can see logs by pages 
> ---------------------------------------------------------------
>
>                 Key: FLINK-13987
>                 URL: https://issues.apache.org/jira/browse/FLINK-13987
>             Project: Flink
>          Issue Type: New Feature
>          Components: Runtime / REST
>            Reporter: lining
>            Priority: Major
>
> As log files becoming more large, current log api often blocks or don't work.
> It's unfriendly for user. As application runs on jvm, sometime user need see 
> log of gc.
> Above all, we need new apis:
>  * /taskmanagers/taskmanagerid/logs -> list all log file
>  * /taskmanagers/taskmanagerid/logs/:filename?start=[start]&count=[count]
>  * /jobmanager/logs -> list all log file
>  * /jobmanager/logs/:filename?start=[start]&count=[count]



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to