Setting the Big Data Protector configuration

After you install the Big Data Protector, you must set the configuration parameters. These parameters will vary depending on the CDP-PVC-Base services that you will use. Protegrity now provides the set_unset_bdp_config.sh script to set the configuration parameters for the required services.

Important: If you want to uninstall the Big Data Protector, then ensure that you roll back the configuration parameters, to their previous values, that you set after installing the Big Data Protector. For more information, refer Restoring the Big Data Protector configuration

To set the Big Data Protector configuration:

1. Log in to the master node of the cluster.

2. Navigate to the directory where you executed configurator script and generated the installation files.

3. To set the configurations using the helper script, run the following command:

   ./set_unset_bdp_config.sh
   

4. Press ENTER.

   The prompt to enter the IP address of the Cloudera Manager server appears.

   Enter Cloudera Manager Server Node's Hostname/IP Address:
   

5. Enter the IP address of the master node.

6. Press ENTER.

   The prompt to enter the name of the cluster appears.

   Enter Cluster's Name:
   

7. Enter the name of the cluster.

8. Press ENTER.

   The prompt to enter the username to access Cloudera Manager appears.

   Enter Cloudera Manager's Username:
   

9. Enter the username.

10. Press ENTER.

    The prompt to enter the password appears.

    Enter Cloudera Manager's Password:
    

11. Enter the password.

12. Press ENTER.

    The script verifies the cluster details and the prompt to set or remove the configuration appears.

    Cluster's existence verified.
    
    Do you want to set or unset the BDP configs?
    [ 1 ] : SET the BDP configs
    [ 2 ] : UNSET the BDP configs
    Enter the no.:
    

13. To set the configuration for the Big Data Protector, type 1.

14. Press ENTER.

    The script updates the configuration for the Big Data Protector.

    Checking existence of HBase service with name 'hbase'.
    
    Service 'hbase' exists.
    
    Setting HBase's config...
    
    ######################################################################################################################################################################### 100.0%
    HBase's 'hbase_coprocessor_region_classes' config for Role Group 'hbase-REGIONSERVER-BASE' has been updated.
    
    ######################################################################################################################################################################### 100.0%
    HBase's 'hbase_coprocessor_region_classes' config for Role Group 'hbase-REGIONSERVER-1' has been updated.
    
    ######################################################################################################################################################################### 100.0%
    HBase's 'hbase_coprocessor_region_classes' config for Role Group 'hbase-REGIONSERVER-2' has been updated.
    
    Checking existence of Hive on Tez service with name 'hive_on_tez'.
    
    Warning: Unable to check existence of Hive on Tez service 'hive_on_tez'. Skipping this service...
    {   
        "message" : "Service 'hive_on_tez' not found in cluster <name_of_the_cluster>."
    }
    
    Checking existence of Tez service with name 'tez'.
    
    Service 'tez' exists.
    
    Setting Tez's config...
    
    ######################################################################################################################################################################### 100.0%
    Tez Service wide config ('tez.cluster.additional.classpath.prefix') has been updated.
    
    Checking existence of Impala service with name 'impala'.
    
    Service 'impala' exists.
    
    Setting Impala's config...
    
    ######################################################################################################################################################################### 100.0%
    Impala's 'IMPALAD_role_env_safety_valve' config for Role Group 'impala-IMPALAD-BASE' has been updated.
    
    ######################################################################################################################################################################### 100.0%
    Impala's 'IMPALAD_role_env_safety_valve' config for Role Group 'impala-IMPALAD-2' has been updated.
    
    ######################################################################################################################################################################### 100.0%
    Impala's 'IMPALAD_role_env_safety_valve' config for Role Group 'impala-IMPALAD-1' has been updated.
    
    Checking existence of Spark on Yarn service with name 'spark_on_yarn'.
    
    Service 'spark_on_yarn' exists.
    
    Setting Spark on Yarn's config...
    
    ######################################################################################################################################################################### 100.0%
    Spark on Yarn Service wide config ('spark-conf/spark-env.sh_service_safety_valve') has been updated.
    
    Checking existence of Spark3 on Yarn service with name 'spark3_on_yarn'.
    
    Service 'spark3_on_yarn' exists.
    
    Setting Spark3 on Yarn's config...
    
    ######################################################################################################################################################################### 100.0%
    Spark3 on Yarn Service wide config ('spark3-conf/spark-env.sh_service_safety_valve') has been updated.
    

To manually set the configuration parameters for the Big Data Protector, refer to the following table:

From v10.0.0 onwards, the BDP pep* jar files will be installed under the /opt/cloudera/parcels/PTY_BDP/bdp/lib/ directory. In addition, the BDP version would be added to the .jar file names.

Warning: Ensure that you do not override the BDP configurations at the client side. Overriding the configurations can result in the component failure.

After you set BDP configurations either by using the helper script or setting them manually, restart the services that are in the Stale configuration state on Cloudera Manager. Ensure to Redeploy the client configuration.