Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-4048

Impala daemon web UI counts EXPIRED sessions in ACTIVE sessions

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: Impala 2.5.0
    • Fix Version/s: Impala 2.8.0
    • Component/s: Backend
    • Labels:

      Description

      Following is the listing of the Impala sessions from Impala daemon Web UI (Screen shot is attached to the issue) . It shows that there are 4 active sessions wherein 3 of the 4 sessions have actually expired. On a large deployment, it can show a lot of active sessions (with most of them as expired) thereby causing users to get concerned. Users need to be able to see non-expired sessions.

      +++++++++++++++++
      Sessions
      There are 4 active sessions.

      <Keeping fewer columns for ease of understanding>

      Session Type Start Time Last Accessed Expired Closed
      HIVESERVER2 2016-08-29 15:40:36.515856000 2016-08-29 22:41:01 true false
      HIVESERVER2 2016-08-27 17:41:37.347666000 2016-08-28 00:44:45 true false
      BEESWAX 2016-08-30 15:40:58.809359000 2016-08-30 22:49:57 false false
      HIVESERVER2 2016-08-27 17:40:21.933108000 2016-08-28 00:40:54 true false

      +++++++++++++++++

        Activity

        Show
        henryr Henry Robinson added a comment - Fixed in https://github.com/apache/incubator-impala/commit/c62d8244a4c3c674367dfa90831fc714d869ecb0
        Hide
        szama_impala_6295 Marcell Szabo added a comment -

        Could we consider backporting this to earlier versions as well?
        Thanks

        Show
        szama_impala_6295 Marcell Szabo added a comment - Could we consider backporting this to earlier versions as well? Thanks
        Hide
        henryr Henry Robinson added a comment -

        Mala Chikka Kempanna -

        Good suggestions for 1 and 2.

        For 3., individual sessions may already be closed from the debug /sessions page.

        As regards the release, it seems reasonable for this to go into Impala 2.8.0.

        Show
        henryr Henry Robinson added a comment - Mala Chikka Kempanna - Good suggestions for 1 and 2. For 3., individual sessions may already be closed from the debug /sessions page. As regards the release, it seems reasonable for this to go into Impala 2.8.0.
        Hide
        mala_ck Mala Chikka Kempanna added a comment -

        Also would want to know , which release of impala will these changes go into once planned by engineering team.

        Show
        mala_ck Mala Chikka Kempanna added a comment - Also would want to know , which release of impala will these changes go into once planned by engineering team.
        Hide
        mala_ck Mala Chikka Kempanna added a comment -

        1. It would help to first understand what is the difference between expired session and active session from the server's point of view. And specify this on a debug web UI in short description.

        2. And the ask on this jira is to seperate out the active sessions from the expired sessions with help/description saying what the clients can to do with expired sessions

        3. Option to clean-up expired sessions from webUI

        Show
        mala_ck Mala Chikka Kempanna added a comment - 1. It would help to first understand what is the difference between expired session and active session from the server's point of view. And specify this on a debug web UI in short description. 2. And the ask on this jira is to seperate out the active sessions from the expired sessions with help/description saying what the clients can to do with expired sessions 3. Option to clean-up expired sessions from webUI

          People

          • Assignee:
            henryr Henry Robinson
            Reporter:
            SudarshanS Sudarshan
          • Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development