[
https://issues.apache.org/jira/browse/FLINK-25581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477903#comment-17477903
]
Leonid Ilyevsky commented on FLINK-25581:
-----------------------------------------
[~chesnay] So maybe the jobs that were not archived at all is different issue.
In the beginning, when I just configured archiving, it did not archive
anything. Now I see at least some jobs are archived.
For now, we have a workaround by keeping our own job start/stop history. So we
can spend some time investigating this strange issue.
Maybe you can try to reproduce this in your environment?
Are there any additional parameters I can set to increase the debug detail
level in jobmanager?
> Jobmanager does not archive completed jobs
> ------------------------------------------
>
> Key: FLINK-25581
> URL: https://issues.apache.org/jira/browse/FLINK-25581
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.13.5
> Environment: RHEL 7
> Reporter: Leonid Ilyevsky
> Priority: Major
> Attachments: error.log
>
>
> Jobmanager does not archive completed jobs.
> I configured the upload directory like this:
> jobmanager.archive.fs.dir: file:///liquidnet/shared/flink/completed-jobs
>
> After the job was completed, nothing appeared in that directory.
> The job info was visible in the jobmanager console for one hour, then it
> disappeared, and still there was no files in the configured directory.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
