Pre-Upgrade Steps for MapR Monitoring

Complete the following steps before you upgrade MapR Monitoring Components with or without the MapR Installer.

During an upgrade, a script backs up many of the configuration files. However, it is a best practice to backup the files manually in case an error occurs or if the specific file you customized is not automatically backed up by the script.
Note: This upgrade sequence does not implement security in the MapR Monitoring components. If security needs to be configured, you must generate certain files and copy them to the appropriate nodes after upgrading. The Post-Upgrade Steps for MapR Monitoring provide links to the installation procedures that provide this information.
  1. Before backing up configuration files, ensure that your Elasticsearch and Kibana indexes are not affected by the upgrade:
    Note: This step assumes that log monitoring is configured. You can skip this step if your cluster is not configured for log monitoring.
    1. If you are using Elasticsearch version 2.x, upgrade your Elasticsearch index to version 6. For upgrade information, see: https://www.elastic.co/guide/en/elasticsearch/reference/current/reindex-upgrade.html
      You need to upgrade your Elasticsearch index if your cluster is running a MEP in the range 1.1 through 3.0.4. See the following table. MEPs 1.1 through 3.0.4 use Elasticsearch version 2.3.3. If your cluster is running a MEP in the range 4.0.0 through 5.0.1, you are using Elasticsearch 5.4.1, and you do NOT need to upgrade the index..
      MEP Elasticsearch Version
      6.1.0 6.2.3
      5.0.1 5.4.1
      5.0.0 5.4.1
      4.1.2 5.4.1
      4.1.1 5.4.1
      4.1.0 5.4.1
      4.0.0 5.4.1
      3.0.4 and earlier 2.3.3
      For more information about the MapR Monitoring component versions included in each MEP, see Component Versions for Released MEPs.
    2. Create a snapshot of the Kibana index to capture index information before the upgrade. This information will be restored after the upgrade. For snapshot information, see https://www.elastic.co/guide/en/elasticsearch/reference/5.6/modules-snapshots.html.
  2. Before you upgrade metric monitoring components, create a backup of the configuration files to a location outside your MapR installation directory. The following configuration file lists include files that are commonly used for configuration and may not include every file that you may have customized.
    • Collectd configuration files:
      • /opt/mapr/conf/conf.d/warden.collectd.conf
      • /opt/mapr/collectd/collectd-<version>/etc/collectd.conf
      • /etc/logrotate.d/collectd
    • Grafana configuration files:
      • /opt/mapr/conf/conf.d/warden.grafana.conf
      • /opt/mapr/grafana/grafana-<version>/etc/grafana/grafana.ini
      • /opt/mapr/grafana/grafana- <version>/etc/grafana/ldap.toml
    • OpenTSDB configuration files:
      • /opt/mapr/conf/conf.d/warden.opentsdb.conf
      • /opt/mapr/opentsdb/opentsdb-<version>/etc/opentsdb/opentsdb.conf
      • /opt/mapr/opentsdb/opentsdb-<version>/etc/opentsdb/logback.xml
      • opt/mapr/opentsdb/opentsdb-<version>/bin/tsdb_cluster_mgmt.sh (This file is not automatically backed up.)
    • For Elasticsearch:
      • /opt/mapr/conf/conf.d/warden.elasticsearch.conf
      • /opt/mapr/elasticsearch/elasticsearch-<version>/etc/elasticsearch/elasticsearch.yml
      • /opt/mapr/elasticsearch/elasticsearch-<version>/etc/elasticsearch/logging.yml
      • /opt/mapr/elasticsearch/elasticsearch-<version>/etc/elasticsearch/curator.yml
      • /opt/mapr/elasticsearch/elasticsearch-<version>/etc/elasticsearch/curator_actions/delete_indices.yml (This file is not automatically backed up.)
    • For OpenTSDB:
      • /opt/mapr/conf/conf.d/warden.opentsdb.conf
      • /opt/mapr/opentsdb/opentsdb-<version>/etc/opentsdb/opentsdb.conf
      • /opt/mapr/opentsdb/opentsdb-<version>/etc/opentsdb/logback.xml
      • opt/mapr/opentsdb/opentsdb-<version>/bin/tsdb_cluster_mgmt.sh (This file is not automatically backed up.)
  3. Before you upgrade log monitoring components, create a backup of the following files to a location outside your MapR installation directory. The following configuration file lists include files that are commonly used for configuration and may not include every file that you may have customized.
    • Kibana configuration files:
      • /opt/mapr/conf/conf.d/warden.kibana.conf
      • /opt/mapr/kibana/kibana-<version>/etc/conf/kibana.js
    • fluentd configuration files:
      • /opt/mapr/conf/conf.d/warden.fluentd.conf
      • /opt/mapr/fluentd/fluentd-<version>/etc/fluentd/fluentd.conf
      • /opt/mapr/fluentd/fluentd-<version>/etc/fluentd/es_config.conf
      • /opt/mapr/fluentd/fluentd-<version>/etc/fluentd/maprfs_config.conf
      • /opt/mapr/fluentd/fluentd-<version>/etc/fluentd/grok-patterns
      • /etc/logrotate/fluentd
    • Elasticsearch configuration files:
      • /opt/mapr/conf/conf.d/warden.elasticsearch.conf
      • /opt/mapr/elasticsearch/elasticsearch-<version>/etc/elasticsearch/elasticsearch.yml
      • /opt/mapr/elasticsearch/elasticsearch-<version>/etc/elasticsearch/logging.yml
      • /opt/mapr/elasticsearch/elasticsearch-<version>/etc/elasticsearch/curator.yml
      • /opt/mapr/elasticsearch/elasticsearch-<version>/etc/elasticsearch/curator_actions/delete_indices.yml (This file is not automatically backed up.)
  4. Stop all MapR Monitoring Services on the cluster.
    1. To stop collectd, run the following command:
      maprcli node services -name collectd -nodes <space separated list of hostname/IPaddresses> -action stop
      
    2. To stop Grafana, run the following command:
      maprcli node services -name grafana -nodes <space separated list of hostname/IPaddresses> -action stop
    3. To stop OpenTSDB, run the following command:
      maprcli node services -name opentsdb -nodes <space separated list of hostname/IPaddresses> -action stop
    4. To stop Kibana, run the following command:
      maprcli node services -name kibana -nodes <space separated list of hostname/IPaddresses> -action stop
    5. To stop fluentd, run the following command:
      maprcli node services -name fluentd -nodes <space separated list of hostname/IPaddresses> -action stop
    6. To stop Elasticsearch, run the following command:
      maprcli node services -name elasticsearch -nodes <space separated list of hostname/IPaddresses> -action stop