GitHub user andrewor14 opened a pull request:

    https://github.com/apache/spark/pull/6310

    [SPARK-4134] Dynamic allocation: Tone down kill error messages

    Right now we get a bunch of scary error messages if the user kills 
executors himself (or uses dynamic allocation to do so):
    
    ![screen shot 2015-05-20 at 3 42 38 
pm](https://cloud.githubusercontent.com/assets/2133137/7741351/b8b2abf8-ff32-11e4-9e72-6863ff60c240.png)
    
    This patch tones down these error messages, since these are really not 
errors.
    
    ![screen shot 2015-05-20 at 8 52 15 
pm](https://cloud.githubusercontent.com/assets/2133137/7741360/c309b4ac-ff32-11e4-9359-4b7465b908f1.png)
    
    I could not figure out how to remove the `WARN` at the end from 
`ReliableDeliverySupervisor`. Any input on that will be much appreciated. I 
tested this on a real YARN cluster.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/andrewor14/spark da-tone-down

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/6310.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #6310
    
----
commit d2582be2e5e02adc08512f283def29ab97c31e56
Author: Andrew Or <[email protected]>
Date:   2015-05-20T22:41:23Z

    Tone down scary unrelated error messages on kill

commit c0cfb34170447915af062ad3bfa384322aaac588
Author: Andrew Or <[email protected]>
Date:   2015-05-21T03:46:26Z

    Fix deadlock
    
    We should not askWithReplay in a synchronized block. In this
    particular case, the CoarseGrainedSchedulerBackend actor tried
    to acquire the same lock when replying, leading to a deadlock.

commit 677df8a819902036b7e03bd09a4ef5a6d3c50f7b
Author: Andrew Or <[email protected]>
Date:   2015-05-21T03:52:42Z

    Tone down BlockManagerMasterEndpoint message further

----


---
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