Data Steward Studio Installation and Upgrade
Also available as:

Pre-installation tasks for DP Profiler Agent for HDP 2.6.5 version

Perform these tasks before you try to install the Data Profiler agent on the cluster.

  1. Ensure that you have downloaded the required software from the customer portal, following the instructions provided as part of the product procurement process.

    DSS includes the following parts:

    1. DSS app that needs to be installed on the DataPlane host
    2. Cluster agent software that needs to be installed on every cluster that is managed by DSS. The cluster agent software consists of an MPack package and the profiler service package.
    The MPack package for the DataPlane profiler agent includes MPack files for both the HDP 2.6.5 and HDP 3.0 versions. You need to unzip the package and identify the MPack to use depending on your version of HDP. You can identify the MPack from the name of the file. For example, the HDP 3.x MPack will have the string hdp3 in its name and the HDP 2.6.x MPack will have the string hdp2 in its name. Make sure you use the right MPack corresponding to your HDP version for installation.
  2. Ensure that the clusters are running the required version of HDP.
  3. Ensure that the following HDP components are installed and configured:
    • Atlas
    • Ranger
    • Knox
    • Spark2 and Livy Server2
  4. Make sure the clusters are Kerberos-enabled.
  5. If you plan to sync users from LDAP into Ranger, ensure a dpprofiler user is created in LDAP and synced into Ranger.
  6. Ensure that Ranger integration for HDFS and Hive is enabled.
  7. Make sure that HDFS Audit logging for Ranger is enabled.
  8. Make sure you install Hive client and HDFS client on the machine where you plan to install DataPlane Profiler Agent.
  9. Add the following proxy users details in the custom core-site.xml file as follows:
    hadoop.proxyuser.livy.groups=* hadoop.proxyuser.livy.hosts=* hadoop.proxyuser.knox.groups=* hadoop.proxyuser.knox.hosts=*
  10. Restart the services as required.
  11. Make sure the resource requirements for YARN queues for a default DSS configurations are as follows:
    • RAM should be greater than or equal to 24 GB.
    • CPU Cores should be greater than equal to 12.

    Update the YARN parameters as follows:

    Set the yarn.scheduler.capacity.maximum-am-resource-percent parameter on YARN > Scheduler (let this be x) such that, when multiplied with the total memory in YARN, it should be greater than or equal to 8G.

    The equation appears as follows:

    (x * total_memory_in_yarn) >= 8G

    For example, for 16 GB it is advised to set x to 0.5.

    All these resources must be allocated exclusively for profiler agent and profilers. It is advisable to have a separate queue.

    The requirements mentioned here specify the resource allocation for the installation of DSS without any performance tuning. For more information about tuning, see Tuning Parameters for the Profiler Service.