Open topic with navigation

# Performing the EKS Upgrade - (Conditional) Step 11 - For Intelligence Only

If the `intelligence-namenode=yes` label was applied to the node being drained, perform these two steps:

- Add the `intelligence-namenode=yes` label to one of the new nodes and update the node FDQN in the Reconfigure page of the OMT (HDFS NameNode under the Intelligence tab)

- Log into each of the database nodes and replace the HDFS NameNode value from the previous step to the `Core-site.xml` file located in the `/etc/hadoop/conf/` directory.

  Select the option that applies to your configuration:

  - If Enable Secure Data Transfer with HDFS Cluster is disabled in the Intelligence tab of the OMT Management portal, in the `/etc/hadoop/conf` directory, add the following configurations:

    In the `hdfs-site.xml` file:

        <configuration>
        </configuration>

    In the `core-site.xml` file:

        <configuration>
          <property>
           <name>fs.defaultFS</name>
           <value>hdfs://<namenode>:30820/</value>
          </property>
          <property>
           <name>dfs.namenode.http-address</name>
           <value><namenode>:30070</value>
          </property>
        </configuration>

  - If Enable Secure Data Transfer with HDFS Cluster is enabled in the Intelligence tab of the OMT Management portal, in the `/etc/hadoop/conf` directory.

    If Kerberos Authentication is enabled, reconfigure it by following the Enabling and Configuring Kerberos Authentication procedure before proceeding.

    Navigate to the /`etc/hadoop/conf` directory and add the following configurations:

    In the `hdfs-site.xml` file:

        <configuration>
          <property>
           <name>dfs.http.policy</name>
           <value>HTTPS_ONLY</value>
          </property>
          <property>
           <name>dfs.encrypt.data.transfer</name>
           <value>true</value>
          </property>
        </configuration>

    In the `core-site.xml` file:

        <configuration>
          <property>
           <name>fs.defaultFS</name>
           <value>hdfs://<namenode>:30820/</value>
          </property>
          <property>
           <name>dfs.namenode.https-address</name>
           <value><namenode>:30070</value>
          </property>
        </configuration>

  Change to the following directory:

      cd /opt/vertica/bin/

  Log in as a dbadmin:

      su dbadmin

  Log in to vsql and specify the password when prompted:

      vsql
      [password prompt]

  Next, run the following commands:

      SELECT CLEAR_HDFS_CACHES();
      SELECT VERIFY_HADOOP_CONF_DIR();
      SELECT node_name, node_address, export_address FROM nodes;

  The expected output is:

      Welcome to vsql, the Vertica Analytic Database interactive terminal.

      Type: \h or \? for help with vsql commands
      \g or terminate with semicolon to execute query
      \q to quit

      fusiondb=>
      fusiondb=> SELECT CLEAR_HDFS_CACHES();
      CLEAR_HDFS_CACHES
      ------------------------------------------------------------------------
      Cleared
      (1 row)

      fusiondb=> SELECT VERIFY_HADOOP_CONF_DIR();
      VERIFY_HADOOP_CONF_DIR
      -------------------------------------------------------------------------
      Validation Success
      v_fusiondb_node0001: HadoopConfDir [/etc/hadoop/conf] is valid
      v_fusiondb_node0002: HadoopConfDir [/etc/hadoop/conf] is valid
      v_fusiondb_node0003: HadoopConfDir [/etc/hadoop/conf] is valid

      (3 rows)

      fusiondb=> SELECT node_name, node_address, export_address FROM nodes;
      node_name | node_address | export_address
      -------------------------------------------------------------------------
      v_fusiondb_node0001 | <IP1> | <IP1>
      v_fusiondb_node0002 | <IP2> | <IP2>
      v_fusiondb_node0003 | <IP3> | <IP3>
      (3 rows)

Next Step - Proceed with the rest of the EKS upgrade steps (resume from Step 12 on): Performing the EKS Upgrade