flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "chenliang (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 Sat, 18 Jul 2015 00:11:04 GMT

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

chenliang commented on FLINK-2367:
----------------------------------

one thing can do : 
When running jobs along with writing log info :  this time ,the system could give some error
message to remind: the log info can't be wrote effectively, please check your system 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