hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-9508) MetaStore client socket connection should have a lifetime
Date Fri, 06 Feb 2015 15:31:34 GMT


Hive QA commented on HIVE-9508:

{color:green}Overall{color}: +1 all checks pass

Here are the results of testing the latest attachment:

{color:green}SUCCESS:{color} +1 7483 tests passed

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase

This message is automatically generated.

ATTACHMENT ID: 12696882 - PreCommit-HIVE-TRUNK-Build

> MetaStore client socket connection should have a lifetime
> ---------------------------------------------------------
>                 Key: HIVE-9508
>                 URL:
>             Project: Hive
>          Issue Type: Sub-task
>          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, HIVE-9508.3.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

View raw message