manuzhang commented on PR #41173:
URL: https://github.com/apache/spark/pull/41173#issuecomment-1577878358
@tgravescs any more comments? We are waiting on this patch to fix our
production issue.
--
This is an automated message from the Apache Git Service.
To respond to the message, please
manuzhang commented on PR #41173:
URL: https://github.com/apache/spark/pull/41173#issuecomment-1567611058
@mridulm @dongjoon-hyun any more comments?
--
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
manuzhang commented on PR #41173:
URL: https://github.com/apache/spark/pull/41173#issuecomment-1560490935
@tgravescs could you take another look?
--
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
manuzhang commented on PR #41173:
URL: https://github.com/apache/spark/pull/41173#issuecomment-1553978308
@tgravescs we have seen it quite often when YARN queues were full and the
containers were **immediately preempted after launch**. I've updated the PR
keeping track of containers
manuzhang commented on PR #41173:
URL: https://github.com/apache/spark/pull/41173#issuecomment-1548929007
retest please
--
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
manuzhang commented on PR #41173:
URL: https://github.com/apache/spark/pull/41173#issuecomment-1548830799
cc @tgravescs @jerryshao Please help review.
--
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