GitHub user gss2002 opened a pull request:

    Zeppelin 1516 1546

    ### What is this PR for?
    Livy Interpreter gets a NestedRuntimException when running with Kerberized 
    ERROR [2016-10-11 22:44:47,769] (
    {pool-2-thread-11}[interpretInput]:192) - Interpreter 
    org.springframework.web.client.RestClientException: Error running rest 
call; nested exception is 
org.springframework.web.client.HttpClientErrorException: 404 Not Found 
    at org.apache.zeppelin.livy.LivyHelper.executeHTTP( 
    at org.apache.zeppelin.livy.LivyHelper.executeCommand( 
    at org.apache.zeppelin.livy.LivyHelper.interpret( 
    at org.apache.zeppelin.livy.LivyHelper.interpretInput( 
    ### What type of PR is it?
    [Improvement | Feature | Refactoring]
    ### Todos
    Doc and Merge latest changes from LivyHelper into code base
    ### What is the Jira issue?
    ### How should this be tested?
    Kerberize Hadoop Cluster, Kerberize Livy Server and Enable Security around 
Zeppelin with multi-user and stop/start running LivyServer
    ### Screenshots (if appropriate)
    ### Questions:
    * Does the licenses files need update? n
    * Is there breaking changes for older versions? n
    * Does this needs documentation? n

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

    $ git pull ZEPPELIN-1516_1546

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

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

    This closes #1512
commit 11bcd2d1db02ff2dbb2a8e560e3f09fe37057796
Author: gss2002 <>
Date:   2016-10-11T04:09:23Z

    ZEPPELIN-1516 Static/Singleton for userSessionMaps

commit 93c2b1488f6f3610c28a10537b18e3d394c8f9e2
Author: gss2002 <>
Date:   2016-10-13T16:28:42Z

    ZEPPELIN-1546 Zeppelin Livy Interpreter Session Management Recovery


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 or file a JIRA ticket
with INFRA.

Reply via email to