itskals commented on pull request #29413: URL: https://github.com/apache/spark/pull/29413#issuecomment-675403672
I think the direction to proceed for us, is to get to an agreement that this is worthy problem to solve.... few questions from my side, which can help: 1. _Is the impact of event drops critical for the reliability of spark ?_ [Note: By spark here I mean the base offering core+Dynamic allocation+App status etc] 2. How common is event drop issue that one has got a complaint of from ones experience? 3. What is general remedy one offers? ( it could be general strategy Databricks (or your company) offers to its customers) For the solutions part [if the issue is critical to solve]: 1. what should be the general direction to solve such problems? [auto-detect=> auto-adjust=> auto-heal etc] 2. How much user involvement is acceptable? If we have a quorum, we can decide what can be next steps...... ---------------------------------------------------------------- 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: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
