Skip to content

Commit 003adc2

Browse files
committed
another change to the xref link
1 parent 0c89d8f commit 003adc2

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

  • docs/modules/hbase/pages/troubleshooting

docs/modules/hbase/pages/troubleshooting/index.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ Currently, xref:zookeeper:index.adoc[Zookeeper] stacklets can only be secured us
66
This means, if an application tries to connect to HBase, it would contact Zookeeper to figure the correct HBase nodes to talk to.
77
In a Java world, you would define a `Client` which would carry the Kerberos requirements.
88

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.
1010
This will result in a Kerberos ( authentication ) error.
1111

1212
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

Comments
 (0)