[
https://issues.apache.org/jira/browse/KUDU-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Serbin resolved KUDU-3558.
---------------------------------
Fix Version/s: 1.18.0
Resolution: Fixed
> Error out when ranger subprocess is started with kerberos disabled
> ------------------------------------------------------------------
>
> Key: KUDU-3558
> URL: https://issues.apache.org/jira/browse/KUDU-3558
> Project: Kudu
> Issue Type: Bug
> Reporter: Ashwani Raina
> Assignee: Ashwani Raina
> Priority: Minor
> Fix For: 1.18.0
>
>
> Today, when kudu cluster (with disabled authentication), is started with Kudu
> ranger, the ranger subprocess doesn't start because of missing keytab file.
> We do catch this error but it happens pretty late in java subprocess init
> routine. And sometimes can be pretty confusing during investigation if not
> looking at the right log file.
> The error message looks like this in stderr log file:
> ++
> Exception in thread "main"
> org.apache.kudu.subprocess.KuduSubprocessException: Kudu principal and Keytab
> file must be provided when Kerberos is enabled in Ranger
> at
> org.apache.kudu.subprocess.ranger.authorization.RangerKuduAuthorizer.init(RangerKuduAuthorizer.java:78)
> at
> org.apache.kudu.subprocess.ranger.RangerProtocolHandler.<init>(RangerProtocolHandler.java:45)
> at
> org.apache.kudu.subprocess.ranger.RangerSubprocessMain.main(RangerSubprocessMain.java:39)
> ++
> This Jira will be used to detect this error pretty early in the process and
> log some actionable information inside kudu master logs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
