You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2020/07/24 07:58:06 UTC

[GitHub] [flink] tillrohrmann commented on pull request #12931: [FLINK-18636][rest] Asynchronous close via configurable timeout in seconds for CompletedOperationCache

tillrohrmann commented on pull request #12931:
URL: https://github.com/apache/flink/pull/12931#issuecomment-663396594


   Thanks for creating this PR @Tartarus0zm. Why do you want to introduce this change? Differently asked, what problem are you encountering? Did you submit a job in attached per-job mode and then decide to cancel the job without waiting for the job result? Or did you create a savepoint and while doing this you decide that you no longer need it?
   
   Assuming that this is the case, I think the proper solution would be to distinguish between a normal cluster shut down after the job has terminated where we want to wait that the results are being served and a user induced shut down (e.g. through cancellation) where one does not want to wait for results of asynchronous operations.


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org