Upgrading a Cluster with a Separated Database - spectrum_platform - 23.1

Spectrum Installation Guide for Linux

Product type
Software
Portfolio
Integrate
Locate
Verify
Product family
Spectrum
Product
Spectrum > Spectrum Platform
Version
23.1
Language
English
Product name
Spectrum Technology Platform
Title
Spectrum Installation Guide for Linux
Copyright
2024
First publish date
2007
Last updated
2024-10-24
Published on
2024-10-24T13:40:32.239551
  • Before upgrading, be sure to read the release notes for the new version. The release notes contain a list of known issues, important compatibility information, supported upgrade paths, and module-specific data backup recommendations.
  • Important: If you upgraded to Spectrum Technology Platform 2022.1 from an earlier version of Spectrum, you must reindex the Spectrum 2022.1 search indexes before you upgrade to Spectrum Technology Platform 2023.1. For instructions how to do this, see Reindex 2022.1 Search Indexes before upgrading to 2023.1 under Upgrading you Installation.
  • Make sure that you follow the appropriate upgrade path for the currently installed version of Spectrum that you want to upgrade.
  • Apply all the latest updates available for your operating system, especially those that resolve issues with Java.
  • Important: We recommend that you create a backup before upgrading so that if an error occurs during the upgrade you can recover your flows, security settings, and other settings and customizations.

    To retain customized settings in the wrapper.conf file located in the SpectrumDirectory/server/bin/wrapper directory, you will need to compare the contents of wrapper.conf installed during the upgrade with the contents of the backed up copy of the file. Before upgrading make sure you have backed up all models and property files. You can then manually copy customizations that you want to retain after the upgrade into the updated version of the file. This is particularly important for changes to the initial and maximum Java heap sizes. This release requires Java 11, so corresponding updates to JVM properties should be used.

This procedure describes how to upgrade Spectrum Technology Platform when you have separated the configuration database from the server. To upgrade an environment that has a separated configuration database, you first upgrade the configuration database cluster, then the server cluster.

  1. Back up the server.
    For instructions for creating a backup, see Creating a Backup Manually in the Spectrum Administration Guide.
    Important: We recommend that you create a backup before upgrading, so if an error occurs during the upgrade process you can recover your flows, security settings, and other settings,.
  2. Back up module-specific data for any of these modules if you have them installed. The following module sections may also contain other information that you should read before upgrading.
  3. Stop all the nodes in the server cluster, then stop all the nodes in the configuration database cluster.
    Run the SpectrumDirectory/server/bin/server.stop script to stop server nodes.
    For instructions on stopping a cluster, see Stopping a Cluster.
  4. Check that all Spectrum Java processes have been shut down before you start the upgrade.
    Note: If you have Global Sentry installed, stop the Global Sentry database server by opening the Windows Services Manager and stopping the Global Sentry Database Server service.
  5. On each node in the cluster, run installdb.sh to upgrade the configuration database.
    Note: If the database automatically starts after upgrading a node, stop the configuration database.
  6. After the upgrade is complete, configure each node in the database cluster with the following settings.
    1. Edit the file DatabaseDirectory/repository/spectrum-container.properties as described in Cluster Properties for a Configuration Database Cluster.
    2. Confirm that the settings in the DatabaseDirectory/repository/neo4j.template file match the following settings:
      dbms.active_database=graphdb
      dbms.default_database=graphdb
      dbms.default_listen_address=0.0.0.0
      causal_clustering.discovery_advertised_address=${spectrum.agent.address}
      causal_clustering.enable_pre_voting=false
      dbms.routing.enabled=true
      dbms.routing.listen_address=0.0.0.0
      dbms.routing.advertised_address=${spectrum.agent.address}
  7. Start each node consecutively in the configuration database cluster.
    To start the configuration database, run the DatabaseDirectory/server/bin/server.start script.

Perform the remaining steps to upgrade the server cluster.

  1. Back up the server.
    For instructions on creating a backup, see the Administration Guide.
  2. Check that all Spectrum Java processes on each machine are stopped before you start the upgrade.
    Note: If you have Global Sentry installed, stop the Global Sentry database server by opening the Windows Services Manager and stopping the Global Sentry Database Server service.
  3. Upgrade each node in the server cluster.
  4. On each node, perform the following steps.
    1. Open the file SpectrumDirectory/server/conf/spectrum-container.properties in a text editor and configure the cluster properties.

      For more information, see Cluster Properties.

    2. Open the file SpectrumDirectory/index/opensearch.template and scroll down to the Node Address section.
      • Remove the hash character # to uncomment the following line
        cluster.initial_master_nodes: ${seeds}

        Then edit it to specify the node names in the cluster:

        cluster.initial_master_nodes: node-1,node-2,node-3,...
        Important: This setting must be uncommented when you start the upgraded cluster for the first time.
      • Insert the hash character # to comment out the following line:
        #discovery.type: single-node
    3. Confirm the following settings on each node in the cluster.
  5. Check again that all Spectrum Java processes on each machine are stopped before you start the cluster.
  6. Start each node in the server cluster consecutively.
    Run the SpectrumDirectory/server/bin/server.start script.
    Do not wait for one node to start before starting another node. All nodes must be started at the same time.
    For more information, see Starting a Cluster.
Note: Any job or subflow stored in the system during a server upgrade is marked as exposed to provide the same behavior for those jobs and subflows as before the upgrade. Any job or subflow that is exported prior to the upgrade will not be exposed. Therefore, when importing these jobs or subflows back into the system, you must manually expose the imported job or subflow.

The following modules have post-upgrade steps you need to perform.

Module Post-upgrade
Spatial During an upgrade, the pool size is reset to 4 if set to a lower value. A pool size setting of 4 or more is unaffected. To change the Remote Component Pool Size value after upgrading, open the Management Console and select Resources > Spatial. Change the pool size value and click Save. For details, see Modifying the Pool Size in the Spectrum Spatial Guide.
Context Graph See Upgrade Context Graph or Upgrading a Cluster with Context Graph.

Related reference

If you have changed default Search Index certificate connection properties