hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "zhihai xu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-13960) Session timeout may happen before HIVE_SERVER2_IDLE_SESSION_TIMEOUT for back-to-back synchronous operations.
Date Tue, 07 Jun 2016 03:49:21 GMT

     [ https://issues.apache.org/jira/browse/HIVE-13960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

zhihai xu updated HIVE-13960:
-----------------------------
    Attachment: HIVE-13960.000.patch

> Session timeout may happen before HIVE_SERVER2_IDLE_SESSION_TIMEOUT for back-to-back
synchronous operations.
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-13960
>                 URL: https://issues.apache.org/jira/browse/HIVE-13960
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>            Reporter: zhihai xu
>            Assignee: zhihai xu
>         Attachments: HIVE-13960.000.patch
>
>
> Session timeout may happen before HIVE_SERVER2_IDLE_SESSION_TIMEOUT(hive.server2.idle.session.timeout)
for back-to-back synchronous operations.
> This issue can happen with the following two operations op1 and op2: op2 is a synchronous
long running operation, op2 is running right after op1 is closed.
>  
> 1. closeOperation(op1) is called:
> this will set {{lastIdleTime}} with value System.currentTimeMillis() because {{opHandleSet}}
becomes empty after {{closeOperation}} remove op1 from {{opHandleSet}}.
> 2. op2 is running for long time by calling {{executeStatement}} right after closeOperation(op1)
is called.
> If op2 is running for more than HIVE_SERVER2_IDLE_SESSION_TIMEOUT, then the session will
timeout even when op2 is still running.



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

Mime
View raw message