Configure NameNodes

For both HDFS and Cloudera, you must configure the namenodes.

Configure the Ambari Hadoop NameNodes

The first step to implementing CTE on HDFS is for the HDFS Administrator to compile a list of the DataNode HDFS local file system directories, and create them on the NameNode local file systems. After this, the Administrator must add the NameNodes to an HDFS Host Group:

1. Compile a list of directories specified by dfs.datanode.data.dir. Obtain this from hdfs-site.xml or using Ambari go to:

   HDFS > Configs > Settings > DataNode > DataNode directories

   

2. If these directories do not already exist in the NameNode local file system, create them on each NameNode in your Hadoop cluster.

3. Pass the following information to the Administrator:

   • The directory list and instructions to create a GuardPoint for the HDFS Host Group on each of these directories.

   • Instructions to add the NameNodes IP addresses or host names to the HDFS Host Group.

Create and Configure the Cloudera Hadoop Namenodes and Datanodes

Create the role goups CTE on Cloudera Manager:

1. Create a new role group for the Thales-namenode.

   1. Group Name: thales-namenode

   2. Role Type: NameNode

   3. Copy from: NameNode Default Group

2. Move the name nodes to the group Thales-namenode.

3. Create a new role group for the Thales-datanode.

   1. Group Name: thales-datanode

   2. Role Type: DataNode

   3. Copy from: DataNode Default Group

4. Move the data nodes to the group thales-datanode.

Configure the Thales-namenode group

1. In the NameNode Environment Advanced Configuration Snippet (Safety Valve) dialog, in the thales-namenode field:

   HADOOP_OPTS="-javaagent:/etc/vormetric/hadoop/jar/vormetric-hdfs-agent.jar=voragent"

   Copy

2. In the NameNode Advanced Configuration Snippet (Safety Valve) for hdfs-site.xml, add the following values:

   <property><name>dfs.vte.ioctl.device</name><value>/opt/vormetric/DataSecurityExpert/agent/secfs/ .sec</value></property>
   <property><name>dfs.vte.ioctl.lib</name><value>vorhdfs</value></property>
   <property><name>dfs.vte.rename.check</name><value>true</value></property>
   <property><name>dfs.block.access.token.enable</name><value>true</value></property>

   Copy

Configure the Thales-datanode group

1. In the DataNode Environment Advanced Configuration Snippet (Safety Valve) dialog, in the thales-namenode field:

   HADOOP_OPTS="-javaagent:/etc/vormetric/hadoop/jar/vormetric-hdfs-agent.jar=voragent"

   Copy

2. In the DataNode Advanced Configuration Snippet (Safety Valve) for hdfs-site.xml, add the following values:

   <property><name>dfs.vte.ioctl.device</name><value>/opt/vormetric/DataSecurityExpert/agent/secfs/.sec</value></property>
   <property><name>dfs.vte.ioctl.lib</name><value>vorhdfs</value></property>
   <property><name>dfs.vte.user.push</name><value>true</value></property>
   <property><name>dfs.block.access.token.enable</name><value>true</value></property>

   Copy