Installing Additional Core Features
Some features can require additional configuration or the installation of additional packages after an upgrade to a new release.
Enabling the Control System After an Upgrade
Some configurations get updated in newer releases/patches. After an upgrade, the Control System could fail to start if the upgraded file is not available.
Use the following steps to avoid Control System startup issues after an upgrade:
- Navigate to the
/opt/mapr/apiserver/conf/
directory:cd /opt/mapr/apiserver/conf/
- Manually merge new configurations from the
/opt/mapr/apiserver/conf.new
file into the existing configurations in/opt/mapr/apiserver/conf
file. This is an essential step for the new configuration in the patch to take effect. - Rename the current
hazelcast.xml
file as follows:mv hazelcast.xml hazelcast.xml.bkp
- Copy the upgraded
hazelcast.xml
file from the/conf.new
directory to the/conf
directory:cp /opt/mapr/apiserver/conf.new/hazelcast.xml .
- Restart the Control System API server after merging the
configurations:
maprcli node services -name apiserver -action restart -nodes <apiserver_node_name>
Restoring Object Store Configuration Files
Upgrades from release 7.0.0 to 7.1.0 or later remove the Object Store configuration files
in /opt/mapr/conf
. This can prevent the Object Store from starting after
the upgrade.
Preparing to Upgrade Core instructed you to create a backup of these files:
moss.conf
s3cfg
moss-core-site.xml
/opt/mapr/conf
on any
node running the MOSS server.Installing the HPE Ezmeral Data Fabric Object Store After an Upgrade
Release 7.0.0 added the HPE Ezmeral Data Fabric Object Store. If you upgraded
from a release earlier than release 7.0.0, use the following steps to install the Object
Store:
- Install the
mapr-s3server
package on all cluster nodes. For more information about installing cluster service packages, see Step 4: Install Cluster Service Packages. - Enable Object Store support if it is not already
enabled:
maprcli cluster feature enable -name cldb.objectstore.support -force true -json
- Restart the CLDB services on the CLDB secondary
nodes:
For more information about node services, see node services./opt/mapr/bin/maprcli node services -cldb restart -nodes node1 node2 node3
- Generate the Object Store certificates by using the
manageSSLKeys.sh
:- After upgrading from core 6.2.0 to 7.0.0 or
later:
In this command,manageSSLKeys.sh createusercert -a moss -u *.<domain_name> -ug <cluster_admin_id>:<cluster_admin_group>
-u
specifies the domain name. - After upgrading from core 6.1.x to 7.0.0 or
later:
manageSSLKeys.sh createusercerts -ug <cluster_admin_id>:<cluster_admin_group> -N <cluster_name>
- After upgrading from core 6.2.0 to 7.0.0 or
later:
- Complete all steps in Enabling the HPE Ezmeral Data Fabric Object Store.
Installing Monitoring After an Upgrade
Monitoring, also known as the Spyglass initiative, provides
the ability to collect, store, and view metrics and logs for nodes, services, and
jobs/applications. You can only install Monitoring after you
upgrade ecosystem components.
- To install Monitoring without the Installer, see Step 9: Install Metrics Monitoring and Step 10: Install Log Monitoring.