[
https://issues.apache.org/jira/browse/IMPALA-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17888346#comment-17888346
]
ASF subversion and git services commented on IMPALA-12852:
----------------------------------------------------------
Commit c10e74d1fc6f8b6759af6cc07894488620f9d68a in impala's branch
refs/heads/master from Michael Smith
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=c10e74d1f ]
IMPALA-13132: Stop Kudu in kill-all.sh
After IMPALA-12852, Kudu is no longer explicitly stopped as part of
kill-all.sh. Kudu stops anyway, but the PID files are not cleaned up.
That can lead to Kudu startup accidentally stopping another process that
re-used the PID when the minicluster is restarted after data load.
Change-Id: I4c40d881140658e8213f742d52e4eb73261e1b30
Reviewed-on: http://gerrit.cloudera.org:8080/21915
Reviewed-by: Joe McDonnell <[email protected]>
Reviewed-by: Wenzhe Zhou <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Separate start_mini_dfs.sh and start_kudu.sh
> --------------------------------------------
>
> Key: IMPALA-12852
> URL: https://issues.apache.org/jira/browse/IMPALA-12852
> Project: IMPALA
> Issue Type: Task
> Reporter: YifanZhang
> Priority: Minor
> Fix For: Impala 4.4.0
>
>
> Currently, we run 'start_mini_dfs.sh' to start several services, including
> hdfs, kms, yarn, and kudu. Considering that Kudu can start and stop
> independently, we should have start_kudu.sh and stop_kudu.sh for convenient
> start and stop for Kudu service.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
