You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zeppelin.apache.org by "Harel Ben Attia (JIRA)" <ji...@apache.org> on 2019/04/24 13:06:00 UTC

[jira] [Created] (ZEPPELIN-4133) Idle sessions are no longer being closed even though TimeoutLifecycleManagement is configured properly

Harel Ben Attia created ZEPPELIN-4133:
-----------------------------------------

             Summary: Idle sessions are no longer being closed even though TimeoutLifecycleManagement is configured properly
                 Key: ZEPPELIN-4133
                 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4133
             Project: Zeppelin
          Issue Type: Bug
          Components: zeppelin-zengine
    Affects Versions: 0.8.0
            Reporter: Harel Ben Attia


Sometimes the timer thread which is initialized by the TimeoutLifecycleManager crashes. This leads to zeppelin not clearing any timedout sessions until a server restart is performed.

The underlying mechanism uses a java Timer (inside TimeoutLifecycleManager.java). We are not sure what had caused the TimerThread thread to crash, since it swallows exceptions/errors. However, a jstack comparison between the server and another zeppelin server which was working well had shown that there is a missing TimerThread thread in the problematic server (1 TimerThread thread vs. 2 TimerThreads). After restarting the zeppelin server, jstack started showing 2 TimerThread threads in its output.

Running on jdk 1.8.0_151, ubuntu 14.04, EC2.

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)