Apache
/
hbase
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

HBASE-20512 document change to running tests on secure clusters 

Signed-off-by: Tak Lon (Stephen) Wu
Signed-off-by: Sean Busbey <busbey@apache.org>
This commit is contained in:
Michael Stack 2018-07-31 13:42:26 -07:00
parent 7f3d9f6f9c
commit 695182bfe3
1 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
src/main/asciidoc/_chapters/upgrading.adoc
View File

@ -611,6 +611,19 @@ Performance is also an area that is now under active review so look forward to
improvement in coming releases (See
link:https://issues.apache.org/jira/browse/HBASE-20188[HBASE-20188 TESTING Performance]).
[[upgrade2.0.it.kerberos]]
.Integration Tests and Kerberos
Integration Tests (`IntegrationTests*`) used to rely on the Kerberos credential cache
for authentication against secured clusters. This used to lead to tests failing due
to authentication failures when the tickets in the credential cache expired.
As of hbase-2.0.0 (and hbase-1.3.0+), the integration test clients will make use
of the configuration properties `hbase.client.keytab.file` and
`hbase.client.kerberos.principal`. They are required. The clients will perform a
login from the configured keytab file and automatically refresh the credentials
in the background for the process lifetime (See
link:https://issues.apache.org/jira/browse/HBASE-16231[HBASE-16231]).
////
This would be a good place to link to an appendix on migrating applications
////
@ -731,6 +744,11 @@ Notes:
Doing a raw scan will now return results that have expired according to TTL settings.
[[upgrade1.3]]
=== Upgrading from pre-1.3 to 1.3+
If running Integration Tests under Kerberos, see <<upgrade2.0.it.kerberos>>.
[[upgrade1.0]]
=== Upgrading to 1.x