One improvement suggestion: “flink-xx-jobmanager-linux-3lsu.log" file can't auto be recovered/detected after mistaking delete

["Chenliang (Liang, DataSight)" <ch...@huawei.com>]

One improvement suggestion, please check if it is valid?

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.


Regards
Liang

Re: One improvement suggestion: “flink-xx-jobmanager-linux-3lsu.log" file can't auto be recovered/detected after mistaking delete

[Maximilian Michels <mx...@apache.org>]

Hi Chenliang,

I've posted a comment in the associated JIRA issue:
https://issues.apache.org/jira/browse/FLINK-2367

Thanks,
Max

On Fri, Jul 17, 2015 at 8:27 AM, Chenliang (Liang, DataSight) <
chenliang613@huawei.com> wrote:

>  *One improvement suggestion, please check if it is valid?*
>
>
>
> 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.
>
>
>
>
>
> Regards
>
> Liang
>