tgravescs commented on pull request #30650: URL: https://github.com/apache/spark/pull/30650#issuecomment-756224716
> Theoretically, the barrier tsm should get scheduled at the end since we have ensured enough slots (via calculateAvailableSlots) before scheduling it. But I'm not sure now is that, maybe in legacy mode, the barrier tsm would hang because of level resetting? (like you mentioned above). I need to think more about this. Yeah I was thinking if something else was using the slots or with the legacy locality, generally you would expect that to whatever is using that slot to finish eventually so it shouldn't be infinite in that case. I think if we add the log message at info level we can leave and deal with it if it becomes a real issue. ---------------------------------------------------------------- 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]
