flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maximilian Michels (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-2367) “flink-xx-jobmanager-linux-3lsu.log" file can't auto be recovered/detected after mistaking delete
Date Fri, 17 Jul 2015 13:15:05 GMT

    [ https://issues.apache.org/jira/browse/FLINK-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631319#comment-14631319
] 

Maximilian Michels commented on FLINK-2367:
-------------------------------------------

Thank you for the suggestion. So the problem is that the log file does not get recreated if
it is deleted while the job manager is running? I'm not sure whether we can prevent this problem.

Our logging framework (log4j) creates a file handle when Flink starts and continues to use
this handle. If you delete the file, the handle still exists and it can still be used for
logging. I think on Windows it is not possible to delete a used file but Unix systems allow
it.

I think you should not modify/delete/move the log file while Flink is running. Even if we
would support that, it could result in an incomplete or inconsistent log file.

> “flink-xx-jobmanager-linux-3lsu.log" file can't auto be recovered/detected after mistaking
delete
> -------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-2367
>                 URL: https://issues.apache.org/jira/browse/FLINK-2367
>             Project: Flink
>          Issue Type: Improvement
>          Components: JobManager
>    Affects Versions: 0.9
>         Environment: Linux
>            Reporter: chenliang
>            Priority: Minor
>              Labels: reliability
>             Fix For: 0.9.0
>
>
> For checking system whether be adequately reliability, testers usually designedly do
some delete operation.
> Steps:
> 1.go to "flink\build-target\log" 
> 2.delete “flink-xx-jobmanager-linux-3lsu.log" file 
> 3.Run jobs along with writing log info, meanwhile the system didn't give any error info
when the log info can't be wrote correctly.
> 4.when some jobs be run failed , go to check log file for finding the reason, can't find
the log file. 
> Must restart Job Manager to regenerate the log file, then continue to run jobs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message