Thesharing commented on pull request #19275: URL: https://github.com/apache/flink/pull/19275#issuecomment-1085598840
> One other point that came up which I'd like to share: If the user enables the history server, I'd suppose that he/she has a strong desire for the result to be in there. That would be another reason why we would consider the HistoryServer in that case a "first-level" citizen next to the `ExecutionGraphInfoStore` which should be populated before actually triggering the cleanup phase. I get it. If the users met the worst case like I mentioned before, he/she can just turn off the archive. Just for my information: would it try to archive the ExecutionGraph once again before it re-triggers another resource cleanup? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
