Configuring Datameer

Configuring a Cluster 

Viewing the Current Configuration

To access the cluster configuration, click "Admin" and select "Cluster Configuration". The configuration page opens. The current cluster settings are displayed. 

Editing the Configuration

To edit the current cluster configuration:

1. Click "Edit". The configuration page opens in edit mode. 
    
2. Change the needed information and confirm with "Save". The configuration is finished.
    

Configuring Local Execution Mode

To edit 'Local Execution' settings:

1. Click on "Edit". The configuration page opens. 
    
2. Select "Local Execution" as the cluster mode from the drop-down. 
    
3. Enter the needed default properties in the "Default Hadoop Properties" text box. 
   INFO: A property contains of a property name and a value. 
   INFO: Delete a name and value pair to delete a property. 
    
4. Enter the needed specific properties in the "Hadoop Distribution Specific Properties" text box. 
    
5. Enter the needed custom properties in the "Custom Properties" text box. 
    
6. Confirm with "Save". The configuration is finished. 
    

Configuring the Hadoop Cluster 

To edit 'Hadoop Cluster' settings:

1. Click on "Edit". The configuration page opens. 
    
2. Select "Hadoop Cluster" as the cluster mode from the drop-down. 
    
3. Enter the needed default properties in the "Default Hadoop Properties" text box. 
   INFO: A property contains of a property name and a value. 
   INFO: Delete a name and value pair to delete a property. 
    
4. Enter the needed specific properties in the "Hadoop Distribution Specific Properties" text box. 
    
5. Enter the needed custom properties in the "Custom Properties" text box. 
    
6. Confirm with "Save". The configuration is finished. 
   

1. Click the Admin tab.
2. Click the Hadoop Cluster tab at the left side. The current settings are shown.
3. Click Edit to make changes.
4. Select Hadoop Cluster for the mode.
   

5. Specify the name node and add a private folder path or use impersonation if applicable.
   Whitespaces aren't supported for use in file/folder paths. Avoid setting up Datameer X storage directories (storage root path, temp paths, execution framework specific staging directories, etc.) with a whitespace in the path.

   Impersonation notes:
   - There is one-to-one mapping between the Datameer X user and the OS user.  
   - The OS user who is launching the Datameer X process must be a sudoer.
   - The temp folder for the Datameer X installation local file system as well as in the Hadoop cluster (for Datameer) should have read/write access.

   • • <Datameer_Installation_Folder>/tmp (Local FileSystem)
     • <Datameer_Private_Folder>/temp (Hadoop Cluster and MapR)

   Learn about /wiki/spaces/DASSB70/pages/33036121028 with Datameer.

   

6. Specify YARN settings.
   

7. Use the properties text boxes to add Hadoop and custom properties. 
   Enter a name and value to add a property, or delete a name and value pair to delete the property.

   Within these edit fields, backslash (\) characters are interpreted by Datameer X as an escape character rather than a plain text character. In order to produce the actual backslash character, you have to type two backslashes:

   example.property=example text, a backslash \\ and further text

   The second backslash is needed as you are effectively editing a Java properties file in these edit fields.

   
   

8. Logging options. Select the severity of messages to be logged. The logging customization field allows to record exactly what is needed.
   
9. Click Save when you are finished making changes.

Kerberos secured Hadoop

Prerequisites:

• Mapping 1:1 the Datameer X Service Account between hosts (Datameer X and all HDFS nodes)
• Adding the Datameer X service account to the HDFS supergroup

• Utilizing the correct krb5.conf in order for Datameer X to communicate with the key distribution center (KDC) correctly. By default, Datameer X assumes that the file is in /etc/krb5.conf on the Datameer X application server. If the file is in another location, specify the path.

  etc/das-env.sh

  export JAVA_OPTIONS="$JAVA_OPTIONS -Djava.security.krb5.conf=/home/datameer/krb5.conf"

To edit settings for a Kerberos secured Hadoop cluster:

1. Click the Admin tab
2. Click the Hadoop Cluster tab at the left side. The current settings are shown.
3. Click Edit to make changes and choose Kerberos Secured Hadoop in the Mode list if needed. Click the link in the dialog box to learn more.
   
4. Specify the URI for the name node, the private folder Datameer X should use, whether impersonation should be enabled, and whether to enable HDFS transparent encryption.
   
5. Enter the necessary Kerberos information: the Kerberos principal for the Datameer X user, the path to the keytab containing Kerberos secrets, the Kerberos principal for YARN, the Kerberos principal for HDFS, and the Kerberos principal for MapReduce.
   
6. Use the Custom Properties text box to add custom properties. Enter a name and value to add a property, or delete a name and value pair to delete that property.
   
7. Logging options. Select the severity of messages to be logged. It is also possible to write custom log settings to record exactly what is needed.
   

8. Click Save when you are finished making changes.

Autoconfigure grid mode 

In Autoconfigure Grid Mode, Datameer X evaluates your cluster and automatically configures the optimal Hadoop cluster settings. You connect Datameer X to your Hadoop cluster by installing a properly configured Hadoop client package on the Datameer X server (using an installation manager such as ClouderaM or Ambari or manually) and then providing Datameer X with a path to that client. 

The Autoconfigure Grid Mode reads all the cluster's property files and evaluates the following properties:

spark.master
das.yarn.available-node-memory
das.yarn.available-node-vcores
spark.yarn.am.cores
spark.yarn.am.memory
spark.yarn.am.memoryOverhead
spark.driver.cores
spark.driver.memory
spark.yarn.driver.memoryOverhead
spark.executor.cores
spark.yarn.executor.memoryOverhead
das.spark.context.max-executors
das.spark.context.auto-scale-enabled
spark.executor.memory
spark.submit.deployMode

You can connect Datameer X to a Hadoop cluster by installing a properly configured Hadoop client package on the Datameer X server (using an installation manager such as ClouderaM or Ambari or manually) and then providing Datameer X with a path to that client. 

1. Go to Admin tab > Hadoop Cluster.
2. Select Autoconfigure Cluster in the Mode field.
3. In the Hadoop Configuration Directory field, enter the directory where the configuration files for Hadoop are located.
4. Enter the path to the folder where Datameer X puts its private information in Hadoop's file system in the Datameer X Private Folder field. 
    
   
5. Enter the number of concurrent jobs.
6. Select whether to use secure impersonation. 
7. Edit the Hadoop or custom properties as necessary.
   If the yarn.timeline-service.enabled property is true in the Hadoop conf files, set yarn.timeline-service.enabled=false as a custom property. (This change is not needed as of Datameer X v6.1)
    
   
8. Click Save.

To update your Datameer X Autoconfig Grid Mode cluster configuration, click Edit on the Hadoop Cluster page and click Save. After saving has been completed, the updated configuration has been applied. New updates to the settings are not shown in the conductor.log but are displayed when clicking again on Edit for Autoconfigure Grid Mode under the Hadoop Properties label.

MapR

To edit settings for clusters using MapR:

1. Click the Admin tab at the top of the page.
2. Click the Hadoop Cluster tab at the left side. The current settings are shown.
3. Click Edit to make changes and choose MapR in the mode list.
   

4. Add the cluster name, the Datameer X private folder, and check the boxes if using /wiki/spaces/DASSB70/pages/33036121047 for Datameer X to submit jobs and access the HDFS on behalf of Datameer X user, and the Max Concurrent jobs. 
    
   There is one-to-one mapping between the Datameer X user and the OS user.  
   The OS user who is launching the Datameer X process must be a sudoer.
   The temp folder for the Datameer X installation local file system as well as in the hadoop cluster (for Datameer) should have read/write access.

   • • <Datameer_Installation_Folder>/tmp (Local FileSystem)
     • <Datameer_Private_Folder>/temp (Hadoop Cluster and MapR)

   Connecting to a secure MapR cluster

   1) Obtain the MapR ticket for the user who is running the Datameer X application. Execute the following command on the shell:

   maprlogin password -user <user_who_starts_datameer>

   2) Install Datameer X and open <Datameer_Home>/etc/das-env.sh and add the following system property to the Java arguments:

   -Dmapr.secure.mode=true

   3) Start and configure Datameer X using MapR Grid Mode.

   The option to connect using Secure Impersonation is now available.

   

   4) (Optional) If there is a failure in saving the configuration:

   Caused by: java.io.IOException: Can't get Master Kerberos principal for use as renewer

   Add the following custom Hadoop properties under the Hadoop Admin page: 

   yarn.resourcemanager.principal=<value>

   The value for this property can be found in the yarn-site.xml file in your Hadoop cluster configuration.

   The steps to achieve impersonation are same as for a secured Kerberos cluster.

5. If required, enter properties. Enter a name and value to add a property, or delete a name and value pair to delete that property.
   
6. Logging options. Select the severity of messages to be logged. It is also possible to write custom log settings to record exactly what is needed.
   
7. Click Save when you are finished making changes.

Configuring High Availability

HDFS NameNode (NN)

Setting a HA enabled Hadoop cluster with Datameer X is almost same as setting an ordinary Hadoop Cluster with following customizations:

1. Specify the NameService to which the Datameer instance should be working with in HDFS NameNode text box: hdfs://nameservice1

2. Specify the following Hadoop properties in Custom Property field:

   Custom Properties

   ### HDFS Name Node (NN) High Availability (HA) ###
   dfs.nameservices=nameservice1
   dfs.ha.namenodes.nameservice1=nn1,nn2
   dfs.namenode.rpc-address.nameservice1.nn1=<server-address>:8020
   dfs.namenode.rpc-address.nameservice1.nn2=<server-address>:8020
   dfs.client.failover.proxy.provider.nameservice1=org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider

   If HDFS HA is configured for automatic failover by using Quorum Journal Manager (QJM), you need to add the following additional custom properties:

   ### HDFS HA Autotmatic Failover
   # By using the Quorum Journal Manager (QJM)
   dfs.ha.automatic-failover.enabled=true
   ha.zookeeper.quorum=<zookeepperHost1>.<domain>.<tld>:2181,<zookeepperHostn>.<domain>.<tld>:2181

3. Check the current NameNode (NN) setting within the database:

   mysql -udap -pdap dap -Bse "SELECT uri FROM data" | cut -d"/" -f3 | sort | uniq

   The command above should have only one result, the former <host>.<domain>.<tld>:<port> value configured under Admin tab > Hadoop Cluster > Storage Settings > HDFS NameNode.
   

4. Update the paths to the new location in the Datameer X DB:

   ./bin/update_paths.sh hdfs://<old.namenode>:8020/<root-path> hdfs://nameservice1/<root-path>

5.  Check to ensure the new NameNode has been applied to the database and that the path is correct:

   mysql -udap -pdap dap -Bse "SELECT uri FROM data" | cut -d"/" -f3,4,5 | sort | uni

   The command above has only one result, the virtual NameNode value including the path configured under Admin tab > Hadoop Cluster > Storage Settings > Datameer Private Folder.

YARN

1. Specify the resource manager with which the Datameer X instance should be working in Yarn Resource Manager Address field: yarnRM.

    

     YARN Application Classpath is a comma-separated list of CLASSPATH entries.

   
   

2. Specify the following Hadoop properties in Custom Property field:

   Custom Properties

   ### Resource Manager (RM) YARN High Availability (HA) ###
   yarn.resourcemanager.cluster-id=yarnRM
   yarn.resourcemanager.ha.enabled=true
   yarn.resourcemanager.ha.rm-ids=rm1,rm2
   yarn.resourcemanager.recovery.enabled=true
   yarn.resourcemanager.store.class=org.apache.hadoop.yarn.server.resourcemanager.recovery.ZKRMStateStore
   yarn.resourcemanager.zk-address=<server-adress>:2181
   ## RM1 ##
   yarn.resourcemanager.hostname.rm1=<server>
   yarn.resourcemanager.address.rm1=<server-adress>:8032
   yarn.resourcemanager.scheduler.address.rm1=<server-adress>:8030
   yarn.resourcemanager.webapp.address.rm1=<server-adress>:8088
   yarn.resourcemanager.resource-tracker.address.rm1=<server-adress>:8031
   ## RM2 ##
   yarn.resourcemanager.hostname.rm2=<server>
   yarn.resourcemanager.address.rm2=<server-adress>:8032
   yarn.resourcemanager.scheduler.address.rm2=<server-adress>:8030
   yarn.resourcemanager.webapp.address.rm2=<server-adress>:8088
   yarn.resourcemanager.resource-tracker.address.rm2=<server-adress>:8031

Configuring Number of Hadoop Cluster Nodes

Datameer X per default, utilizes all nodes within the Hadoop cluster. This might conflict with Datameer X users under a node-based license that have more nodes in their cluster than their contract allows. Control the number of nodes Datameer X interacts with using a VCore (virtual cores) allocation method. 

VCore allocation method 1 (recommended)

Comply with a node-based license by configuring Datameer X to recognize a specific number of vcores from nodes within the Hadoop cluster. 

1. Add all available vcores from both head and worker nodes.
2. Divide total number of vcores by the number of nodes in the cluster. This average constitutes the size of a single node. (If the node-based license allows 3 nodes, 3 times the average number of vcores can be used.)

3. Update the YARN scheduler on the Hadoop cluster to the number of specified vcores.

   yarn.scheduler.capacity.<queue_name>.maximum-allocation-vcores=12

4.  Add a /wiki/spaces/DASSB70/pages/33036120688 to recognize the number of available vcores.

   For Tez:

   tez.queue.name=<queue_name>

   For Spark:

   spark.yarn.queue=<queue_name>

VCore allocation method 2

Add a /wiki/spaces/DASSB70/pages/33036120688 to recognize the number of available vcores.

yarn.nodemanager.resource.cpu-vcores:4  

This isn't the preferred method as latency can be an issue when searching for data stored on a non-named node.

Encrypting Data on Transport

Datameer X doesn't require any configuration changes when working with an SSL enabled cluster, however in MR2 architecture Datameer X uses the ResourceManager webserver to get node and cluster metrics.

For this to work properly, the Java TrustStore and its password must be accessible to the Datameer X application.

1. Add the following system properties:

   etc/das-env.sh

   export JAVA_OPTIONS="$JAVA_OPTIONS -Djavax.net.ssl.trustStore=${JAVA_HOME}/jre/lib/security/cacerts -Djavax.net.ssl.trustStorePassword=<password>"

2. Optional: To configure the HTTP endpoint for YARN daemons, set the following values:

   Custom Properties

   ### HTTP Policy ###
   yarn.http.policy=HTTPS_ONLY

3. Optional: If Resource Manager (RM) High Availability is configured, set the following properties:

   Custom Properties

   ## RM1 ##
   yarn.resourcemanager.webapp.https.address.rm1=<server-adress>:8090
   ## RM2 ##
   yarn.resourcemanager.webapp.https.address.rm2=<server-adress>:8090

4. Optional: If your key management server (KMS) also serves using HTTPS and is configured to do so in /etc/hadoop-kms/conf/kms-site.xml, set in the following properties:

   Custom Properties

   hadoop.security.key.provider.path=kms://https@<host>:16000/kms
   dfs.encryption.key.provider.uri=kms://https@<host>:16000/kms
   tez.dag.recovery.enabled=false

   For more information see Hadoop in Secure Mode - Data Confidentiality, Securing the Key Management Server (KMS), and Managing Key Trustee Server Certificates. 

Temporary Folder

Datameer's <datameer-install-path>/tmp folder stores temporary files required for Datameer. 

/wiki/spaces/DASSB70/pages/33036120749

# Move the cache for workbook-previews and dfs
sed -i "s/\(localfs.cache-root=\).*\$/\1\/var\/cache\/datameer/" conf/default.properties

After completing the recommended configuration, the temp file is left with three directories as well as a cache of specific framework plug-ins. These directories are required and can't be moved or purged. 

Folders:

• das-plugins<id>.folder - A cache of all installed plug-ins.
• start<id>.properties - Datameer's startup configuration.
• jetty-0.0.0.0-8080-conductor-_-any-<id>.dir - A working directory for the embedded Jetty web service.

Example cache file of a framework plug-in:

• tmp/tez-plugin-jars

If the /tmp folder is consuming too much space and other files are present in the folder, Datameer X suggests it is safe to purge files that are older than three days.

Distributed File System Cache

Datameer's Distributed File System cache <datameer-install-path>cache/dfscache is used for or caching data link and import job sample records as well as log and jdbc files.

Datameer's default settings clean dfscache entries when the threshold passes 10,000.

dfscache configuration settings can be found in modules/dap-common/src/main/resources/ehcache.xml.

 <cache
        name="dfsCache"
        maxEntriesLocalHeap="10000"
        timeToIdleSeconds="60"
        timeToLiveSeconds="60"
        eternal="false"
        diskPersistent="false"
        overflowToDisk="false"
    >

This dfscache grows in size as the number of sample records from import jobs and data links is increased. Follow the troubleshooting guide if the Datameer X filesystem is full due to excessive reduce-part-#### files generated in dfsCache folder.

The dfscache folder and its contents can be moved to a different location if needed by following the guide in our knowledge base.

Configuring Time Zones

Define the time zone that should be used for displaying the date in the UI and for parsing date strings that do not specify a timezone. Use default as the value to use the local server's time zone.

In conf/default.properties you can change the value designating the time zone:

If the time zone is changed on the machine where Datameer X is running, Datameer X must be restarted to show the new default time zone configuration.

Examples