You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Ashwani Raina (Jira)" <ji...@apache.org> on 2024/02/28 13:28:00 UTC
[jira] [Created] (KUDU-3558) Error out when ranger subprocess is started with kerberos disabled
Ashwani Raina created KUDU-3558:
-----------------------------------
Summary: 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
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)