Recreating Hive metadata after decommissioning a node

After removing/decommissioning a node that stored the Hive metadata, truncate the Hive metadata table, then recreate the table.

After removing/decommissioning a node that stored the Hive metadata, truncate the Hive metadata table, then recreate the table. In the hive-site.xml file, set the parameters as shown in the following example to specify a different keyspace and table for the Hive metastore:

There are two instances of the hive-site.xml file.

For use with Spark, the default location of the hive-site.xml file is:

Installer-Services and Package installations /etc/dse/spark/hive-site.xml
Installer-No Services and Tarball installations install_location/resources/spark/conf/hive-site.xml

For use with Hive, the default location of the hive-site.xml file is:

Installer-Services and Package installations /etc/dse/hive/hive-site.xml
Installer-No Services and Tarball installations install_location/resources/hive/conf/hive-site.xml
<property>
    <name>cassandra.connection.metaStoreKeyspaceName</name>
    <value>newKeyspaceName</value>
  </property>
  <property>
    <name>cassandra.connection.metaStoreColumnFamilyName</name>
    <value>MetaStore</value>
  </property>

This action is necessary to prevent an exception in SemanticAnalyzer.genFileSinkPlan.

After decommissioning a node in an analytics datacenter, run the dsetool cleanup_leases command to clear old LeaderManager entries.