You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Gary Yao (Jira)" <ji...@apache.org> on 2020/01/16 11:46:00 UTC

[jira] [Closed] (FLINK-15489) Cannot update jobmanager/taskmanager logs

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

Gary Yao closed FLINK-15489.
----------------------------
    Fix Version/s: 1.9.2
       Resolution: Fixed

1.9: 6a124f8be8b73f686033a1b89d934ec7b334bb9f
1.10: 6a124f8be8b73f686033a1b89d934ec7b334bb9f
master: 871266781814066d4a81fd0a4c30b877cbcc11a2

> Cannot update jobmanager/taskmanager logs
> -----------------------------------------
>
>                 Key: FLINK-15489
>                 URL: https://issues.apache.org/jira/browse/FLINK-15489
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Web Frontend
>    Affects Versions: 1.9.1, 1.10.0
>            Reporter: Dawid Wysakowicz
>            Assignee: Yadong Xie
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 1.9.2, 1.10.0
>
>         Attachments: 6E9A4D72-6664-4B00-B02F-57EB2695D967.png, 7A1CF604-032D-46D8-AC70-FBB884E868B9.png, screenshot-1.png, screenshot-2.png
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> There is no way to query the latest state of logs of jobmanager/taskmanager.
> The Web UI show only the first version that was ever displayed.
> How to reproduce:
> * (not sure if necessary) configure logback as described here: https://ci.apache.org/projects/flink/flink-docs-stable/dev/best_practices.html#use-logback-when-running-flink-on-a-cluster
> * start a cluster
> * show jobmanager logs in the Web UI
> * run example job
> * check again the jobmanager logs, there is no trace of the job. Clicking the refresh button does not help



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