PDFs

On this page:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
39 rates
You can upgrade a Controller instance from 4.4.3 to latest on AWS by using the Enterprise Console CLI. The Enterprise Console simplifies the upgrade process by allowing you to discover and upgrade single Controllers and HA-pairs. See Upgrade the Controller Using the Enterprise Console for more information.

You can also move the Controller to a new EC2 instance to meet updated performance requirements.

Upgrade the Controller on AWS from 4.4.3 to Latest

Before upgrading the Controller, you should take a backup of the Aurora database instance. You should also ensure that you have an Amazon Machine Image (AMI) that accurately reflects the current Controller instance. 

The Enterprise Console upgrades the schema to the latest version. However, upgrading the Controller does not upgrade the Aurora DB server.

You can use the Enterprise Console upgrade command to upgrade the Controller from 4.4.3 to the latest version by specifying auroraHost as the controllerDBHost:

  1. Run the following command on the Enterprise Console host:

    bin/platform-admin.sh submit-job --service controller --job upgrade --args controllerPrimaryHost="<hostname>" controllerRootUserPassword="<password>" mysqlRootPassword="<password>" controllerDBHost="auroraDBHost" databaseType=aurora

    If your upgrade fails, you can resume by passing the flag useCheckpoint=true as an argument after --args.

  2. Update the AMI after the job finishes.

Rollback to a Previous AMI

If a rollback is required, complete the following steps:

  1. Create a new Aurora instance, using the database snapshot you took earlier as the source. 
  2. Stop the upgraded Controller if it is still running:

    bin/platform-admin.sh stop-controller-appserver
  3. Repoint the database DNS alias to the new Aurora instance. 
  4. Terminate the EC2 instance hosting the current Controller. This should cause a new EC2 instance to be provisioned using the existing AMI, with the older Controller version. 
  5. Attach the ENI to the new EC2 instance. 
  6. Verify that the Controller is working as it was before the upgrade. 

Move the Controller on AWS

You can move the Controller to a new EC2 instance by completing the following steps: 

  1. Terminate the EC2 instance hosting the current Controller. This should cause a new EC2 instance to be automatically provisioned using the AMI.

    The auto-scaling group and launch configuration are defined with the AMI. Therefore, if the existing EC2 instance in the auto-scaling group dies, it is automatically replaced with a new EC2 instance based on the same AMI.

  2. Attach the ENI to the new EC2 instance.
  3. Verify that the Controller is working as expected.
  • No labels