Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensuring that Spark Uncaught exceptions are handled in the Snappy side and do not cause a system.exit #342

Merged
merged 5 commits into from
Sep 9, 2016

Commits on Aug 25, 2016

  1. Dont restart the executor if the cache is closing down.

    Hemant Bhanawat committed Aug 25, 2016
    Configuration menu
    Copy the full SHA
    cc0f256 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    a86fcbb View commit details
    Browse the repository at this point in the history

Commits on Aug 29, 2016

  1. SnappyUncaughtExceptionHandler is now set as the uncaught exception h…

    …andler in the executor. SnappyUncaughtExceptionHandler exits the executor component unlike the SparkUncaughtExceptionHandler which does a System.exit.
    
    Added a new test to test the uncaughtexception handler.
    Hemant Bhanawat committed Aug 29, 2016
    Configuration menu
    Copy the full SHA
    cb7f1d7 View commit details
    Browse the repository at this point in the history

Commits on Sep 6, 2016

  1. Merge remote-tracking branch 'origin/master' into SNAP-846

    Conflicts:
    	spark
    Hemant Bhanawat committed Sep 6, 2016
    Configuration menu
    Copy the full SHA
    8d8a4c4 View commit details
    Browse the repository at this point in the history

Commits on Sep 9, 2016

  1. Merge remote-tracking branch 'origin/master' into SNAP-846

    Conflicts:
    	spark
    Hemant Bhanawat committed Sep 9, 2016
    Configuration menu
    Copy the full SHA
    182c2ee View commit details
    Browse the repository at this point in the history