ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nate Cole (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-18568) Hive shows restart indicator after RU
Date Tue, 11 Oct 2016 21:08:21 GMT

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

Nate Cole updated AMBARI-18568:
-------------------------------
    Description: 
After RU including Hive, the Hive service shows a restart indicator.  This is because orchestration
sets up Hive Metastore FIRST, then HiveServer.  HiveServer has config changes for port.

Since metastore has already been restarted before the config change and depends on hive-site,
it reports having stale configs.

Change is only for HDP-2.5

  was:
After RU including Hive, the Hive service shows a restart indicator.  This is because orchestration
sets up Hive Metastore FIRST, then HiveServer.  HiveServer has config changes for port.

Since metastore has already been restarted before the config change and depends on hive-site,
it reports having stale configs.


> Hive shows restart indicator after RU
> -------------------------------------
>
>                 Key: AMBARI-18568
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18568
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Nate Cole
>            Assignee: Nate Cole
>            Priority: Critical
>             Fix For: 2.5.0
>
>
> After RU including Hive, the Hive service shows a restart indicator.  This is because
orchestration sets up Hive Metastore FIRST, then HiveServer.  HiveServer has config changes
for port.
> Since metastore has already been restarted before the config change and depends on hive-site,
it reports having stale configs.
> Change is only for HDP-2.5



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

Mime
View raw message