Liupengcheng cad475dcc9 [SPARK-26941][YARN] Fix incorrect computation of maxNumExecutorFailures in ApplicationMaster for streaming ... ## What changes were proposed in this pull request? Currently, when enabled streaming dynamic allocation for streaming applications, the maxNumExecutorFailures in ApplicationMaster is still computed with `spark.dynamicAllocation.maxExecutors`. Actually, we should consider `spark.streaming.dynamicAllocation.maxExecutors` instead. Related codes: f87153a3ac/resource-managers/yarn/src/main/scala/org/apache/spark/deploy/yarn/ApplicationMaster.scala (L101) ## How was this patch tested? NA Please review http://spark.apache.org/contributing.html before opening a pull request. Closes #23845 from liupc/Fix-incorrect-maxNumExecutorFailures-for-streaming. Lead-authored-by: Liupengcheng <liupengcheng@xiaomi.com> Co-authored-by: liupengcheng <liupengcheng@xiaomi.com> Signed-off-by: Sean Owen <sean.owen@databricks.com>		2019-03-16 19:45:05 -05:00
..
kubernetes	[SPARK-26343][K8S] Try to speed up running local k8s integration tests	2019-03-14 19:39:48 -07:00
mesos	[MINOR][BUILD] Add 2 maven properties(hive.classifier and hive.parquet.group)	2019-03-07 16:46:07 -06:00
yarn	[SPARK-26941][YARN] Fix incorrect computation of maxNumExecutorFailures in ApplicationMaster for streaming	2019-03-16 19:45:05 -05:00