[
https://issues.apache.org/jira/browse/IMPALA-8306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong resolved IMPALA-8306.
-----------------------------------
Fix Version/s: Impala 4.0
Resolution: Fixed
> Debug WebUI's Sessions page verbiage clarification
> --------------------------------------------------
>
> Key: IMPALA-8306
> URL: https://issues.apache.org/jira/browse/IMPALA-8306
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Affects Versions: Impala 2.12.0, Impala 3.1.0
> Reporter: Vincent Tran
> Assignee: Tim Armstrong
> Priority: Minor
> Labels: supportability
> Fix For: Impala 4.0
>
> Attachments: sessions.png
>
>
> Currently, the Debug WebUI's Sessions page captures both active sessions and
> expired sessions. On the top of the page there is a message along the line of:
> {noformat}
> There are {{num_sessions}} sessions, of which {{num_active}} are active.
> Sessions may be closed either when they are idle for some time (see Idle
> Timeout
> below), or if they are deliberately closed, otherwise they are called active.
> {noformat}
> This text is ambiguous for me. If all non-active sessions are expired
> sessions, it should explicitly tell the user that. And since an active
> session becomes an expired session when it breaches the Session Idle Timeout,
> the second sentence is also somewhat misleading. User has to "deliberately
> close" both active sessions and expired sessions to close them.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
