Hi folks, I have updated the description,
this is the new :
As the job running, the log files are becoming 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, i list new api:
-
list taskmanager all log file
- /taskmanagers/taskmanagerid/logs
{
"logs": [
{
"name": "taskmanager.log",
"size": 12529
}
]}
-
see taskmanager log file by range
- /taskmanagers/taskmanagerid/logs/:filename?start=[start]&count=[count]
{
"data": "logcontent",
"file_size": 342882}
-
list jobmananger all log file
- /jobmanager/logs
{
"logs": [
{
"name": "taskmanager.log",
"size": 12529
}
]}
-
see jobmanager log file by range
- /jobmanager/logs/:filename?start=[start]&count=[count]
{
"data": "logcontent",
"file_size": 342882}
lining (Jira) <
[hidden email]> 于2019年9月6日周五 下午3:57写道：
> lining created FLINK-13987:
> ------------------------------
>
> Summary: 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
>
>
> 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]
>
>
>
> --
> This message was sent by Atlassian Jira
> (v8.3.2#803003)
>
Locked
