Upgrading to Cloud Next¶

Acquia contract revisions¶

All environments, applications, and subscriptions upgraded to Cloud Next are subject to the March 31st, 2021 revisions to Acquia’s Support Users Guide and Acquia’s Products & Services Guides (Legacy Server-based Pricing Model, Current Views/Visits Pricing Model), especially as they pertain to Acquia’s Resource Limits on dynamically auto-scaling infrastructure. See all sections related to the use of shared resources, infrastructure capacity, and capacity management for more details.

MySQL Workbench Management Software¶

Currently, MySQL Workbench is not fully compatible with Cloud Next. Therefore, customers who are using it to connect to environments running on Cloud Next must use Sequel Pro.

Alternatively, customers can use the following workaround to connect to your environment:

1. Locate the database credentials listed on your Databases page.
2. In a local terminal, run:

{ssh -L $LOCAL_PORT:$DB_HOST:3306 $SSH_STRING}

Here,

• LOCAL_PORT is the port to which Workbench must connect when using localhost.
• DB_HOST is the hostname obtained from the Cloud Platform user interface.
• SSH_STRING is the full connection string from the Cloud Platform user interface. For example, user@something.

simpleSAMLphp¶

Customers with simpleSAMLphp in an application must make a few changes before upgrading to Cloud Next to ensure ongoing compatibility with both Cloud Classic infrastructure and Cloud Next. For more information, see Implementing SimpleSAML on Cloud Next.

Legacy Keys¶

SSH keys that were manually added to an environment before the October 2018 EOL of per-environment SSH key management will not persist after the upgrade to Cloud Next. If your application was running on Cloud Platform Enterprise before that date, visit the Users & Keys page for each of your application’s environments before they are upgraded. You must ensure that all necessary SSH keys are properly associated with users in your subscription’s Teams & Permissions console.

Failure to do so may result in errors whenever users, scripts, development software, automations, or remote services attempt to access those environments after they are upgraded.

Direct log access¶

The /var/log/sites directory is no longer available for direct log access or custom log storage. Use /shared/logs for custom log storage instead.

Slow queries¶

Long-running MySQL queries will now be terminated after running for 60 seconds on non-production environments or 5 minutes for production environments. To ensure your environments complete all long-running transactions as expected, wrap them in a MySQL transaction to avoid the risk of data loss or corruption. If your environments require long-running MySQL queries to complete reports or other complex data management processes, contact your Acquia accounts team to request a delay to your upgrade to Cloud Next.

Memcache¶

• To avoid slow page load times on Cloud Next, applications with the following line of code (or similar) in any Memcache settings files must be commented out before any environments are upgraded to Cloud Next:

  # REMOVE or comment out any lines similar to this that set OPT_BINARY_PROTOCOL to true.
  $settings['memcache']['options'][Memcached::OPT_BINARY_PROTOCOL] = TRUE;
  

• You must upgrade your Memcache module to the latest version to view Memcache metrics on the memcache_admin page of your Drupal application.

• Environments upgraded to Cloud Next are assigned the Memcache memory limit previously associated with their Cloud Classic infrastructure. As a result, for environments previously deployed on Cloud Classic infrastructure with other environments, this setting may be higher than necessary post-upgrade and may need to be reduced to a lower limit to prevent excess resource utilization.

• Memcached data is available through CLI by using the acquia-memcache stats command. The mcstat command is currently not available on Cloud Next environments.

• To optimize performance for your application after upgrade, access your New Relic APM account and test your environments with Memcache turned on and off during periods of low traffic.

  Applications that are less complex may see even better response times without Memcache on Cloud Next due to improvements to MySQL. You can disable Memcache on Cloud Next environments by navigating to each environment’s Configure Environment page, clicking the Advanced tab, and setting your Memcache memory limit to 0 MB. Some applications may also need to have this line added to the settings.php file to prevent Memcache from running automatically:

  define('AH_NO_MEMCACHE_INCLUDE', 1);

Remote Administration¶

Applications running on Cloud Next should test all Remote Administration patches in a Cloud Next non-production environment before pushing changes to the production environment. This ensures that no differences in Cloud Next and Cloud Classic logic impact the way patches behave after deployment in a Cloud Next environment.

Logic requiring access to a tmp or persistent shared directory must be redirected to $HOME on Cloud Next.