[
https://issues.apache.org/jira/browse/HADOOP-18645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17693384#comment-17693384
]
ASF GitHub Bot commented on HADOOP-18645:
-----------------------------------------
virajjasani opened a new pull request, #5433:
URL: https://github.com/apache/hadoop/pull/5433
```
util.ExitUtil - Exiting with status 1:
org.apache.hadoop.service.ServiceStateException: java.io.IOException: Running
in secure mode, but config doesn't have a keytab
1: org.apache.hadoop.service.ServiceStateException: java.io.IOException:
Running in secure mode, but config doesn't have a keytab
at org.apache.hadoop.util.ExitUtil.terminate(ExitUtil.java:264)
..
..
```
When multiple downstreamers use different configs to present the same keytab
file, if one of the config key gets missing or overridden as part of config
generators, it becomes bit confusing for operators to realize which config is
missing for a particular service, especially when keytab file value is already
present with different config.
It would be nice to report config key with the stacktrace error message.
> Provide keytab file key name with ServiceStateException
> -------------------------------------------------------
>
> Key: HADOOP-18645
> URL: https://issues.apache.org/jira/browse/HADOOP-18645
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Major
>
>
> {code:java}
> util.ExitUtil - Exiting with status 1:
> org.apache.hadoop.service.ServiceStateException: java.io.IOException: Running
> in secure mode, but config doesn't have a keytab
> 1: org.apache.hadoop.service.ServiceStateException: java.io.IOException:
> Running in secure mode, but config doesn't have a keytab
> at org.apache.hadoop.util.ExitUtil.terminate(ExitUtil.java:264)
> ..
> ..
> {code}
>
>
> When multiple downstreamers use different configs to present the same keytab
> file, if one of the config key gets missing or overridden as part of config
> generators, it becomes bit confusing for operators to realize which config is
> missing for a particular service, especially when keytab file value is
> already present with different config.
> It would be nice to report config key with the stacktrace error message.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
