[
https://issues.apache.org/jira/browse/IMPALA-12198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe McDonnell resolved IMPALA-12198.
------------------------------------
Fix Version/s: Impala 4.3.0
Resolution: Fixed
> Create RANGER_LOG_DIR if it doesn't exist for kill-ranger-server.sh
> -------------------------------------------------------------------
>
> Key: IMPALA-12198
> URL: https://issues.apache.org/jira/browse/IMPALA-12198
> Project: IMPALA
> Issue Type: Improvement
> Components: Infrastructure
> Affects Versions: Impala 4.3.0
> Reporter: Joe McDonnell
> Assignee: Joe McDonnell
> Priority: Major
> Fix For: Impala 4.3.0
>
>
> Ranger's ranger-admin-services.sh relies on being able to log to
> $RANGER_LOG_DIR for the stop command. If $RANGER_LOG_DIR doesn't exist (which
> can happen when bin/clean.sh runs), then testdata/bin/kill-ranger-server.sh
> will fail with this error:
> {noformat}
> Getting pid from /tmp/rangeradmin.pid ..
> Found Apache Ranger Admin Service with pid 23263, Stopping it...
> /opt/Impala-Toolchain/cdp_components-40643771/ranger-2.3.0.7.2.18.0-41-admin/ews/ranger-admin-services.sh:
> line 129:
> /home/joemcdonnell/upstream/Impala/logs/cluster/ranger/catalina.out: No such
> file or directory
> Shutdown in progress. Will check after 2 secs again..
> Shutdown in progress. Will check after 2 secs again..
> ...
> Initial kill failed, getting serious now...
> Apache Ranger Admin Service with pid 23263 has been stopped.{noformat}
> The missing directory error means that the original stop command never even
> executed. Ranger will not stop on its own, so this will always wait for 30
> seconds and then do a hard kill. This delays stopping Ranger for no reason.
> If kill-ranger-server.sh creates RANGER_LOG_DIR before running
> ranger-admin-services.sh, then the original stop command succeeds immediately.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
