Verify the DLM Engine installation

Ensure that your DLM Engine set up is functional.

• Scan through Ambari logs of DLM Engine service installation for any errors.
• Run the /usr/dlm/current/beacon/bin/verify_beacon_knox.sh utility script to ensure that Knox SSO is configured successfully with the DLM Engine.
  /usr/dlm/current/beacon/bin/verify_beacon_knox.sh https://<knox_hostname>:8443/gateway/knoxsso/api/v1/websso http://<beacon_hostname>:25968 admin admin
• Verify that Beacon was added as a user to the HDFS superuser group.

  hdfs groups beacon

  The output should display HDFS (or value of the dfs.permissions.superusergroup config) as one of the groups.

• Verify that beacon user is setup as Ranger admin. In secure cluster, this will be ‘beacon’ user with role ‘Admin. In unsecure cluster, this will be ‘beacon_ranger” user with ‘Admin’ role.
  
• Verify that the ‘beacon’ user has Hive access through Ranger policies.

  ‘Beacon’ user has repladmin privileges

  ‘Beacon’ user has access to all databases, tables, and columns.

  

  ‘Beacon’ user can kill Hive queries.

  

  Verify that Hive service is setup with Ranger authoriser and doas=false.

  List of Atlas policies with ‘Beacon’ user on a secure cluster.

  

  Atlas entity policy.

  

  Atlas operation policy.