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

Posted to dev@lens.apache.org by "Barun Kumar (JIRA)" <ji...@apache.org> on 2018/08/09 13:46:00 UTC

[jira] [Commented] (LENS-1527) Fix session restore issue

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

Barun Kumar commented on LENS-1527:
-----------------------------------

Review req: https://reviews.apache.org/r/68279/

> 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
>
> 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)