yangwwei commented on pull request #34672: URL: https://github.com/apache/spark/pull/34672#issuecomment-1007823318
hi @tgravescs thanks for getting back on this one : ). I think @attilapiros already mentioned > But it got sidetracked and become stale. Based on this experience I am afraid the ideal solution is a bit far away in the future. @attilapiros please share your thoughts. I understand this may not be the best/elegant solution, but it is simple and it works. I do not think hacking more things in the remote shuffle service side is better, this is a common problem that should be handled on the Spark side. If there is a better, actionable solution, I would love to explore more. -- 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: reviews-unsubscr...@spark.apache.org 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
