You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Joe McDonnell (Jira)" <ji...@apache.org> on 2022/10/01 03:39:00 UTC
[jira] [Resolved] (IMPALA-11621) testdata/bin/kill-hive-server.sh should remove the HiveServer2 pid file
[ https://issues.apache.org/jira/browse/IMPALA-11621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe McDonnell resolved IMPALA-11621.
------------------------------------
Fix Version/s: Impala 4.2.0
Resolution: Fixed
> testdata/bin/kill-hive-server.sh should remove the HiveServer2 pid file
> -----------------------------------------------------------------------
>
> Key: IMPALA-11621
> URL: https://issues.apache.org/jira/browse/IMPALA-11621
> Project: IMPALA
> Issue Type: Improvement
> Components: Infrastructure
> Affects Versions: Impala 4.2.0
> Reporter: Joe McDonnell
> Assignee: Joe McDonnell
> Priority: Major
> Fix For: Impala 4.2.0
>
>
> With HIVE-22193, Hive added a graceful stop functionality that also changed some startup scripts. Hive now keeps a file with the HiveServer2's pid and checks to see if it is already running before starting up. testdata/bin/kill-hive-server.sh uses testdata/bin/kill-java-service.sh, and it doesn't know to remove the pid file. Since testdata/bin/kill-java-service.sh would fail if it was unable to stop HiveServer2, it should be safe to remove the pid file after that command succeeds.
> If we don't remove the pid file, the OS might reuse the pid and this could interfere with HiveServer2 startup.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)