Mammoth Webhcat Cluster Verification Test Fails when Sentry Synchronization is Enabled on BDA V4.2 (Doc ID 2095496.1)

Last updated on JANUARY 15, 2016

Applies to:

Big Data Appliance Integrated Software - Version 4.2.0 and later
Linux x86-64

Symptoms

The Mammoth webcat cluster verification test fails on BDA V4.2 when Sentry Synchronization is Enabled.

The webhcat_test.out file shows the following.

Running a Webhcat test -- creating a test database and a test table
Start running webhcat test
Wait for hcat server to be up...
HTTP/1.1 401 Authentication required
WWW-Authenticate: Negotiate
Set-Cookie: hadoop.auth=; Path=/; Expires=Thu, 01-Jan-1970 00:00:00 GMT; HttpOnly
Cache-Control: must-revalidate,no-cache,no-store
Content-Type: text/html;charset=ISO-8859-1
Content-Length: 1314
Server: Jetty(7.6.0.v20120127)

HTTP/1.1 200 OK
Set-Cookie: hadoop.auth="u=oracle&p=oracle/bdatestuser@EXAMPLE.COM&t=kerberos&e=*&s=*/*="; Path=/; Expires=Thu, 17-Dec-2015 08:13:30 GMT; HttpOnly
Content-Type: application/json
Transfer-Encoding: chunked
Server: Jetty(7.6.0.v20120127)

{"version":"v1","status":"ok"}
-------------------------------------------------------------------------------
TEST: create a hcatlog database directory
Successfully created Hcatalog database directory
Could not change permissions on Hcatalog database directory
Webhcat test failed

 

Changes

 Enabling Sentry Synchronization by setting "dfs.namenode.acls.enabled" and "Enable Sentry Synchronization"  causes the issue.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms