[
https://issues.apache.org/jira/browse/KUDU-3504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17755734#comment-17755734
]
ASF subversion and git services commented on KUDU-3504:
-------------------------------------------------------
Commit 0a9c9e7f81d9e0e63501fc98652027a8ea2dae69 in kudu's branch
refs/heads/master from Attila Bukor
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=0a9c9e7f8 ]
KUDU-3503 Allow extra JVM arguments
This commit introduces a new flag to provide extra JVM arguments to the
Ranger subprocess.
Its test also test the new behavior of crashing the master when a
subprocess dies introduced with KUDU-3504.
Change-Id: I60f82e8a2fe106b267da3d2acd71a61e5a46a759
Reviewed-on: http://gerrit.cloudera.org:8080/20347
Tested-by: Kudu Jenkins
Reviewed-by: Alexey Serbin <ale...@apache.org>
> Crash master on subprocess failure
> ----------------------------------
>
> Key: KUDU-3504
> URL: https://issues.apache.org/jira/browse/KUDU-3504
> Project: Kudu
> Issue Type: Improvement
> Reporter: Attila Bukor
> Assignee: Attila Bukor
> Priority: Major
>
> If the Ranger subprocess crashes, authorization will fail, but there's no
> other indication that the process has died. The master won't restart the
> subprocess and there's no way to restart it manually without restarting Kudu
> anyway. Furthermore, if the subprocess crashes, that's likely a symptom of
> something that requires manual intervention to resolve to avoid crashing in
> the future, so it's best if the master crashes upon the subprocess crashing
> as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
