Github user mkhaitman commented on the pull request:

    https://github.com/apache/spark/pull/7532#issuecomment-133127541
  
    Been testing this merged PR specifically and it looks great so far :). One 
thing I noticed however is that the TaskSchedulerImpl throws and error once an 
executor has been lost, even if that's the expected behaviour of using Dynamic 
Allocation. Would it make more sense to produce a warning as opposed to error 
in the scenario that the executor is dropped as a result of executor idle 
timeout? 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to