You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hive.apache.org by "Thiruvel Thirumoolan (JIRA)" <ji...@apache.org> on 2015/02/03 13:20:34 UTC

[jira] [Updated] (HIVE-9508) MetaStore client socket connection should have a lifetime

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

Thiruvel Thirumoolan updated HIVE-9508:
---------------------------------------
    Attachment: HIVE-9508.2.patch

Uploading another version of patch with the functionality enabled and a minor bug fix.

> MetaStore client socket connection should have a lifetime
> ---------------------------------------------------------
>
>                 Key: HIVE-9508
>                 URL: https://issues.apache.org/jira/browse/HIVE-9508
>             Project: Hive
>          Issue Type: Improvement
>          Components: CLI, Metastore
>            Reporter: Thiruvel Thirumoolan
>            Assignee: Thiruvel Thirumoolan
>              Labels: metastore, rolling_upgrade
>             Fix For: 1.2.0
>
>         Attachments: HIVE-9508.1.patch, HIVE-9508.2.patch
>
>
> Currently HiveMetaStoreClient (or SessionHMSC) is connected to one Metastore server until the connection is closed or there is a problem. I would like to introduce the concept of a MetaStore client socket life time. The MS client will reconnect if the socket lifetime is reached. This will help during rolling upgrade of Metastore.
> When there are multiple Metastore servers behind a VIP (load balancer), it is easy to take one server out of rotation and wait for 10+ mins for all existing connections will die down (if the lifetime is 5mins say) and the server can be updated.



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