Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Fri, 2 Dec 2016 14:19:58 +0000 (UTC)
From: "Stephan Ewen (JIRA)" <jira@apache.org>
To: issues@flink.apache.org
Message-ID: <JIRA.13025095.1480688349000.423792.1480688398435@Atlassian.JIRA>
In-Reply-To: <JIRA.13025095.1480688349000@Atlassian.JIRA>
References: <JIRA.13025095.1480688349000@Atlassian.JIRA> <JIRA.13025095.1480688349453@arcas>
Subject: [jira] [Created] (FLINK-5232) Add a Thread default uncaught
 exception handler on the JobManager
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 02 Dec 2016 14:20:00 -0000

Stephan Ewen created FLINK-5232:
-----------------------------------

             Summary: Add a Thread default uncaught exception handler on the JobManager
                 Key: FLINK-5232
                 URL: https://issues.apache.org/jira/browse/FLINK-5232
             Project: Flink
          Issue Type: Sub-task
          Components: JobManager
            Reporter: Stephan Ewen
             Fix For: 1.1.3


When some JobManager threads die because of uncaught exceptions, we should bring down the JobManager. If a thread dies from an uncaught exception, there is a high chance that the JobManager becomes dysfunctional.

The only sfae thing is to rely on the JobManager being restarted by YARN / Mesos / Kubernetes / etc.

I suggest to add this code to the JobManager launch:

{code}
Thread.setDefaultUncaughtExceptionHandler(new UncaughtExceptionHandler() {

    @Override
    public void uncaughtException(Thread t, Throwable e) {
        try {
            LOG.error("Thread {} died due to an uncaught exception. Killing process.", t.getName());
        } finally {
            Runtime.getRuntime().halt(-1);
        }
    }
});
{code}


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)