Skip to content
18 changes: 18 additions & 0 deletions docs/modules/hbase/pages/troubleshooting/index.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
= Troubleshooting

== Hbase access with kerberos authentication
Comment thread
Maleware marked this conversation as resolved.
Outdated

Currently, xref:zookeeper:index.adoc[Zookeeper] is not secured with authentication. This means, if an application tries to connect to Hbase, it would ask the zookeeper quorum to figure the correct nodes to talk to. In a Java world, you would define a `Client` which would carry the kerberos requirements.
Comment thread
Maleware marked this conversation as resolved.
Outdated

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. This will result in a kerberos ( authentication ) error.
Comment thread
Maleware marked this conversation as resolved.
Outdated

To prevent this, you can set a jvm argument like ( again e.g. SparkApplications )
Comment thread
Maleware marked this conversation as resolved.
Outdated
Comment thread
Maleware marked this conversation as resolved.
Outdated

[source,yaml]
----
jvmArgumentOverrides:
add:
- "-Dzookeeper.sasl.client=false"
Comment thread
Maleware marked this conversation as resolved.
Outdated
----

in all pods which would like to talk to Hbase.
Comment thread
Maleware marked this conversation as resolved.
Outdated
1 change: 1 addition & 0 deletions docs/modules/hbase/partials/nav.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -25,3 +25,4 @@
** xref:hbase:reference/discovery.adoc[]
** xref:hbase:reference/commandline-parameters.adoc[]
** xref:hbase:reference/environment-variables.adoc[]
* xref:hbase:troubleshooting/index.adoc[]
Loading