[ 
https://issues.apache.org/jira/browse/LENS-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575981#comment-16575981
 ] 

Hudson commented on LENS-1527:
------------------------------

SUCCESS: Integrated in Jenkins build Lens-Commit #1484 (See 
[https://builds.apache.org/job/Lens-Commit/1484/])
LENS-1527 : Fix session restore issue (rajitha.r: rev 
11885b9812ecce9093c18259084de2c6c5ccbb02)
* (edit) lens-server/src/test/resources/lens-site.xml
* (edit) 
lens-server/src/main/java/org/apache/lens/server/session/HiveSessionService.java
* (edit) lens-server/src/main/java/org/apache/lens/server/BaseLensService.java
* (edit) 
lens-server-api/src/main/java/org/apache/lens/server/api/session/SessionService.java


> Fix session restore issue
> -------------------------
>
>                 Key: LENS-1527
>                 URL: https://issues.apache.org/jira/browse/LENS-1527
>             Project: Apache Lens
>          Issue Type: Bug
>          Components: api, server
>            Reporter: Barun Kumar
>            Assignee: Barun Kumar
>            Priority: Major
>             Fix For: 2.8
>
>         Attachments: LENS-1527_1.patch
>
>
> When a session is created in Lens, corresponding hive session is created for 
> cluster user and session count map for user is updated. But when Lens is 
> started and restores it's sessions, the session count map is updated for 
> cluster user.
>  
> Since many user may have same cluster user, on restart of Lens the session 
> count for cluster user will be a lot and if you try to create session using 
> that cluster user, you might get 429(which is sent when session limit is 
> exhausted for a user).
> The fix for this is while resotring the session, use loggedin user to update 
> the session count map.



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

Reply via email to