Pivotal® Greenplum® Text v2.3.1

Upgrading GPText

Upgrading a GPText system to a new GPText release installs the new GPText software release on all hosts in the Greenplum cluster and then upgrades the GPText system.

Upgrading GPText and Greenplum Database at the Same Time

If you are upgrading to new releases of Greenplum Database and GPText at the same time, follow these steps:

  1. Complete the Greenplum Database upgrade first and ensure the database is operational.
  2. Run the GPText gptext-migrator utility to migrate your current GPText system to the newly upgraded Greenplum Database system.
  3. Ensure that the current version of GPText works with the new Greenplum Database version.
  4. Proceed with the GPText upgrade.

Upgrading a GPText Release

Upgrading a GPText release is a two-part process: install the new software release on the Greenplum cluster hosts and then upgrade the existing GPText system. The GPText installer performs the first part, installing the new software. The gptext-upgrade utility performs the second part, upgrading the current GPText system to the new version.

The GPText installer detects an existing GPText system and, after installing the new software release, offers to run the gptext-upgrade utility for you. If you choose to upgrade the GPText system later, you can run the gptext-upgrade utility yourself.

All upgrade tasks are executed on the Greenplum master host as the gpadmin user. The gpadmin user must have write permission in the directory where the new GPText release is to be installed, /usr/local/greenplum-text-<release>-<version> by default.

The Greenplum Database, ZooKeeper, and GPText clusters must be running. The procedure stops and restarts GPText during the upgrade.

Follow these steps:

  1. Download the new GPText release for your platform from Pivotal Network.

  2. Extract the release package.

    $ tar xfz greenplum-text-<version>-<platform>.tar.gz
  3. Make sure that ZooKeeper and GPText are running.

    $ gptext-state
  4. Run the GPText installer.

    $ ./greenplum-text-<version>-<platform>.bin

    When upgrading GPText, you do not specify an installation configuration file as you do for the initial GPText installation.

  5. The installer prompts you to accept the Pivotal license agreement and to choose and create the installation directory.

  6. The installer verifies the environment to ensure that prerequisites are present, such as Python and Java. If any problems are discovered, the installer outputs an error message and stops. Correct the problem identified by the message and run the installer again.

  7. After the new software has been installed on the Greenplum cluster, the installer looks for an existing GPText installation. If an existing GPText system is found, the installer asks if you wish to upgrade GPText directly.

    • If you answer yes, the installer runs the gptext-upgrade script. The gptext-upgrade utility validates the environment to ensure it can complete the upgrade, then executes the upgrade and restarts the GPText system. If any problems are discovered, gptext-upgrade outputs a message and quits. Fix the indicated problems and run the gptext-upgrade utility (at <NEW_GPTEXTHOME>/bin/gptext-upgrade) to complete the GPText system upgrade.
    • If you answer no, you must run the gptext-upgrade script after the installer completes. See the gptext-upgrade utility reference for instructions.

    Important: If you answer no or if the gptext-upgrade quits without upgrading your software, follow these steps to re-run gptext-upgrade at a later time:

    1. Source the script in the old GPText installation directory. For example:
      $ source /usr/local/greenplum-text-<old-version>/
    2. Run the gptext-upgrade command from the new GPText installation directory:
      $ /usr/local/greenplum-text-<new-version>/bin/gptext-upgrade

  8. After the upgrade has completed, source the in the new GPText release directory and run gptext-state healthcheck to verify the GPText system:

    $ source /usr/local/greenplum-text-<version>/
    $ gptext-state healthcheck