You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Andrew Onischuk (JIRA)" <ji...@apache.org> on 2015/05/20 19:00:00 UTC

[jira] [Resolved] (AMBARI-11271) Move hiveserver2 beeline check to Hive SC and do mupliple other service-level optimizations

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

Andrew Onischuk resolved AMBARI-11271.
--------------------------------------
    Resolution: Fixed

Committed to trunk

> Move hiveserver2 beeline check to Hive SC and do mupliple other service-level optimizations
> -------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-11271
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11271
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.1.0
>
>
> Currently multiple customers are complaining on high services (re-)start time.
> From what we understood probably more than a minute is bad.
> So after discussion with Mahadev it was decided to move out beeline check
> which takes usually ~2 minutes (resulting in hive restarting in ~4minutes)
> from start to service check, which seems a good place for that.
> There is a problem due to Hive process asynchroniously starts and can drop
> start without Ambari knowing it.  
> Also this was implemented some time ago because of:
>     
>     
>     AMBARI-5800
>     Race condition when starting all services causing Hive service check to fail
>     
> But, since now service check does exactly the beeline check with mutiple
> retries this won't happen
> Test scenarios included:  
> 1\. Restart Hive and rt after it start service check  
> 2\. Restart Hive and rt after it restart Webhcat  
> 3\. Start service check with Hive Server HA



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