You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "chenliang (JIRA)" <ji...@apache.org> on 2015/08/17 20:50:46 UTC
[jira] [Updated] (FLINK-2367) “flink-xx-jobmanager-linux-3lsu.log" file can't auto be recovered/detected after mistaking delete
[ https://issues.apache.org/jira/browse/FLINK-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
chenliang updated FLINK-2367:
-----------------------------
Assignee: chenliang
> “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
> Assignee: 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)