ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srimanth Gunturi (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (AMBARI-12280) HiveServer2 upgrade/downgrade should deregister old server after new one is started
Date Wed, 08 Jul 2015 17:31:04 GMT

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

Srimanth Gunturi reopened AMBARI-12280:
---------------------------------------

> HiveServer2 upgrade/downgrade should deregister old server after new one is started
> -----------------------------------------------------------------------------------
>
>                 Key: AMBARI-12280
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12280
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Srimanth Gunturi
>            Assignee: Srimanth Gunturi
>            Priority: Critical
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-12280.patch, AMBARI-12280_2.patch
>
>
> During upgrade/downgrade, the deregister is happening before the new HS2 is started.
This can lead to a case where there is no HS2 up and running. The order needs to be fixed,
to first start target version of HS2 and then do the deregister.
> 1. Switch hive-server2 to the new software version, start the new process, and deregister
the old version of hive-server2:
> Since the current version would have changed before hive version is obtained for deregister
command, the version should be obtained using the HDP versioned path.
> /usr/hdp/$HDP_VERSION/hive/bin/hive --version 
> It will be safer to use the full path to hive for this, instead of relying on the $PATH
variable setting.



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

Mime
View raw message