You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Adding troubleshooting for kerberos
* Updating xref references
* Adding newline eof
* Add suggestions
Co-authored-by: Sebastian Bernauer <sebastian.bernauer@stackable.de>
* Adding jvm-argument-overrides link
* Fixing link to applications.adoc
* revert changes
* another change to the xref link
* Move troubleshooting to be consistent with other operators
---------
Co-authored-by: Sebastian Bernauer <sebastian.bernauer@stackable.de>
Currently, xref:zookeeper:index.adoc[Zookeeper] stacklets can only be secured using mutual TLS.
6
+
This means, if an application tries to connect to HBase, it would contact Zookeeper to figure the correct HBase nodes to talk to.
7
+
In a Java world, you would define a `Client` which would carry the Kerberos requirements.
8
+
9
+
However, those requirements might be passed through and thus your client (e.g. xref:spark-k8s:usage-guide/operations/applications.adoc[SparkApplications]) would try to authenticate with Kerberos at the corresponding Zookeeper endpoint.
10
+
This will result in a Kerberos ( authentication ) error.
11
+
12
+
To prevent this, you can set a xref:concepts:overrides.adoc#jvm-argument-overrides[JVM argument] like this (again e.g. SparkApplications) in all Pods which would like to talk to HBase:
13
+
14
+
[source,yaml]
15
+
----
16
+
jvmArgumentOverrides:
17
+
add:
18
+
- "-Dzookeeper.sasl.client=false"
19
+
----
20
+
21
+
22
+
== Additional stack-traces
23
+
24
+
To add more useful information to stack-traces caused by RPC issues, the xref:concepts:overrides.adoc#config-overrides[Config overrides documentation] can be used to replace the default Netty implementation:
0 commit comments