[
https://issues.apache.org/jira/browse/LENS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15007672#comment-15007672
]
Raju Bairishetti edited comment on LENS-833 at 11/17/15 12:11 AM:
------------------------------------------------------------------
bq. This is definitely a good feature but I'm wondering what options does the
user have (besides waiting) once this situation is met.
Either user should close one of the old sessions to open a new session or he
should wait for one of the session to be expired.
bq. Sure, we can have an api to expire sessions older than given time for a
user.
[~amareshwari] Does it make sense to have a cli command for killing the
specific session along with user specific session expiry intervals? Right now,
quitting the shell will close the current session.
was (Author: raju.bairishetti):
bq. This is definitely a good feature but I'm wondering what options does the
user have (besides waiting) once this situation is met.
Either user should close one of the old sessions to open a new session or he
should wait for one of the session to be expired.
bq. Sure, we can have an api to expire sessions older than given time for a
user.
[~amareshwari] Does it make sense to have a cli command for killing the
specific session? Right now, quitting the shell will close the current session.
> Limit number of open sessions per user on session service
> ---------------------------------------------------------
>
> Key: LENS-833
> URL: https://issues.apache.org/jira/browse/LENS-833
> Project: Apache Lens
> Issue Type: New Feature
> Components: server
> Reporter: Amareshwari Sriramadasu
> Assignee: Raju Bairishetti
> Fix For: 2.5
>
>
> We should fail open session if user creates more sessions than configured
> limit.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
