tgravescs commented on pull request #29413: URL: https://github.com/apache/spark/pull/29413#issuecomment-675474599
From my experience: 1) For the dynamic allocation it definitely is, but in my opinion the right solution there is to pull the dynamic allocation manager into the core scheduler and not rely on the messages and listener queues. I have not seen direct issues with others. 2) In my previous experience it was very uncommon and adjust queue sizes worked. But I also had increased the default size of the queue along with the default memory of the driver to be larger at a cluster config level. ---------------------------------------------------------------- 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: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
