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
Copy file name to clipboardExpand all lines: docs/modules/hbase/pages/troubleshooting/index.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ Currently, xref:zookeeper:index.adoc[Zookeeper] stacklets can only be secured us
6
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
7
In a Java world, you would define a `Client` which would carry the Kerberos requirements.
8
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.
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
10
This will result in a Kerberos ( authentication ) error.
11
11
12
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:
0 commit comments