You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lens.apache.org by "Raju Bairishetti (JIRA)" <ji...@apache.org> on 2016/09/22 00:05:22 UTC

[jira] [Commented] (LENS-1290) Number of open sessions for a user are going beyond his max defined limit

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

Raju Bairishetti commented on LENS-1290:
----------------------------------------

[~puneet884] Right now, we are decrementing the session count when a client closes session. But internally, LensService is not closing session immediately in case if the session has active queries.

We should decement the session count for user only if session is actually closed. It would be better if we can have a separate counter for number of sessions are in *closeInProgress* state(i.e. markedForClose ). We can publish this counter and currently active session count  to client as part of MaxSessionLimitReached excpetion message. So that client will know exactly why he is not able to open a new session.

> Number of open sessions for a user are going beyond his max defined limit
> -------------------------------------------------------------------------
>
>                 Key: LENS-1290
>                 URL: https://issues.apache.org/jira/browse/LENS-1290
>             Project: Apache Lens
>          Issue Type: Bug
>          Components: server
>            Reporter: Puneet Gupta
>            Assignee: Puneet Gupta
>         Attachments: open sessions.png
>
>
> Max Sessions for a user is configured as 100 . Seeing 200+  open sessions for a user. Same is happing for other users too which 100+ open sessions. 
>  <property>
>     <name>lens.server.max.sessions.per.user</name>
>     <value>100</value>
>  </property>



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