[
https://issues.apache.org/jira/browse/FLINK-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14700016#comment-14700016
]
chenliang commented on FLINK-2367:
----------------------------------
ok, your explanation looks reasonable. how about adding some note: "log file
deleted during runtime is not supported to be aware, this deletion operation
belongs OS behavior, please manually check if the written log file still
exists".
> “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)
