Hi Anyang, thanks for your suggestions.
1) I guess one needs to make this interval configurable. A session cluster could theoretically execute batch as well as streaming tasks and, hence, I doubt that there is an optimal value. Maybe the default could be a bit longer than 1 min, though. 2) Which component to do you want to let terminate immediately? I think we can consider your input while reviewing the PR. If it would be a bigger change, then it would be best to create a follow up issue once FLINK-10868 has been merged. Cheers, Till On Fri, Sep 6, 2019 at 11:42 AM Anyang Hu <huanyang1...@gmail.com> wrote: > Thank you for the reply and look forward to the advice of Till. > > Anyang > > Peter Huang <huangzhenqiu0...@gmail.com> 于2019年9月5日周四 下午11:53写道： > >> Hi Anyang, >> >> Thanks for raising it up. I think it is reasonable as what you requested >> is needed for batch. Let's wait for Till to give some more input. >> >> >> >> Best Regards >> Peter Huang >> >> On Thu, Sep 5, 2019 at 7:02 AM Anyang Hu <huanyang1...@gmail.com> wrote: >> >>> Hi Peter&Till: >>> >>> As commented in the issue >>> <https://issues.apache.org/jira/browse/FLINK-10868#>，We have introduced >>> the FLINK-10868 <https://issues.apache.org/jira/browse/FLINK-10868> patch >>> (mainly batch tasks) online, what do you think of the following two >>> suggestions: >>> >>> 1) Parameter control time interval. At present, the default time >>> interval of 1 min is used, which is too short for batch tasks; >>> >>> 2)Parameter Control When the failed Container number reaches >>> MAXIMUM_WORKERS_FAILURE_RATE and JM disconnects whether to perform >>> OnFatalError so that the batch tasks can exit as soon as possible. >>> >>> Best regards, >>> Anyang >>> >>
