hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl Steinbach (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-3590) TCP KeepAlive and connection timeout for the HiveServer
Date Wed, 17 Oct 2012 09:34:04 GMT

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

Carl Steinbach commented on HIVE-3590:
--------------------------------------

+1. Will commit in a day if tests pass and no one requests more time for review.
                
> TCP KeepAlive and connection timeout for the HiveServer
> -------------------------------------------------------
>
>                 Key: HIVE-3590
>                 URL: https://issues.apache.org/jira/browse/HIVE-3590
>             Project: Hive
>          Issue Type: Improvement
>          Components: Server Infrastructure
>            Reporter: Esteban Gutierrez
>            Assignee: Esteban Gutierrez
>            Priority: Critical
>              Labels: patch
>             Fix For: 0.10.0
>
>         Attachments: HIVE-3590.1.patch, HIVE-3590.2.patch
>
>
> Simple implementation of TCP KeepAlive and socket timeout for the HiveServer in order
to avoid half open connections or connection drops during long running queries that use HiveServer.
> Two new settings have been added in order to control this functionality.
> {code}
> <property>
>    <name>hive.server.read.socket.timeout</name>
>    <value>10</value>
>    <description>Timeout for the HiveServer to close the connection if no response
from the client in N seconds, defaults to 10 seconds.</description>
> </property>
> <property>
>    <name>hive.server.tcp.keepalive</name>
>    <value>true</value>
>    <description>Whether to enable TCP keepalive for the HiveServer. Keepalive will
prevent accumulation of half-open connections.</description>
> </property>
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message