You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Dmytro Sen (JIRA)" <ji...@apache.org> on 2014/11/14 14:12:33 UTC

[jira] [Resolved] (AMBARI-8332) Configs: Hive client retry settings are not adequate

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

Dmytro Sen resolved AMBARI-8332.
--------------------------------
    Resolution: Fixed

Committed to trunk and branch-1.7.0

> Configs: Hive client retry settings are not adequate
> ----------------------------------------------------
>
>                 Key: AMBARI-8332
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8332
>             Project: Ambari
>          Issue Type: Bug
>          Components: stacks
>    Affects Versions: 1.7.0
>         Environment: HDP2.2
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Blocker
>             Fix For: 1.7.0
>
>
> Currently hive client retry settings are recommended to be:
> {code}
> hive.metastore.failure.retries=5
> hive.metastore.client.connect.retry.delay=5
> {code}
> So we have overall time of 25 seconds to restart Hive. This doesn't seem reasonable in a rolling upgrade scenario where we accomplish three things:
> {noformat}
> - Stop the Hive metastore
> - Upgrade the schema (run the schemaTool upgrade)
> - Start the Hive metastore
> {noformat}
> For now I think we should raise it to 2 minutes. We could do the following:
> {code}
> hive.metastore.failure.retries=24
> hive.metastore.connect.retries=24
> hive.metastore.client.connect.retry.delay=5s
> {code}



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