Changes

• Reduced timeout for Gateway's caches to acquire a connection to Swarm Storage nodes. This avoids incoming connections triggering file handle limits with threads stuck in ScspObjectCache, requiring a "systemctl cloudgateway restart". (CLOUD-3853)

• Gateway 8.1.0 is required when using a search feed created with Swarm 16.1.2 search.perDomainIndex=True. No gateway.cfg changes are needed. Please remember to restart Gateway whenever the default search feed is changed. (CLOUD-3988)

Upgrade Impacts

See Upgrading Gateway to upgrade from a version of Gateway 6 or 7. See Upgrading from Gateway 5.x, if migrating from Elasticsearch 2.3.3 and Gateway 5.

Starting with Gateway 7.8, Elasticsearch 6.8.6 is no longer supported. Remain on Gateway 7.7 until the rolling upgrade from Elasticsearch 6.8.6 to 7.5.2 is completed.

Address the upgrade impacts for this and each prior version since the currently running version:

Impacts for 8.0.4

• Version Requirements

  • Swarm Storage 14.1.0 or higher

  • Elasticsearch 7.5.2 or 7.17.9 (required with Swarm Storage 15.3 or higher)

  • Content UI 7.9.1

  • Storage UI 3.5.0

Impacts for 8.0.3

• Version Requirements

  • Swarm Storage 14.1.0 or higher

  • Elasticsearch 7.5.2 or 7.17.9 (required with Swarm Storage 15.3 or higher)

  • Content UI 7.9.1

  • Storage UI 3.5.0

Impacts for 8.0.2

• Version Requirements

  • Swarm Storage 14.1.0 or higher

  • Elasticsearch 7.5.2 or 7.17.9 (required with Swarm Storage 15.3 or higher)

  • Content UI 7.9.1

  • Storage UI 3.5.0

Impacts for 8.0.1

• Version Requirements

  • Swarm Storage 14.1.0 or higher

  • Elasticsearch 7.5.2 or 7.17.9 (required with Swarm Storage 15.3 or higher)

  • Content UI 7.9.1

  • Storage UI 3.5.0

See Content Gateway 7 Release Notes and Content Gateway 6 Release Notes for impacts from prior releases.

Watch Items and Issues

These are known operational limitations that exist for Gateway.

• When using the default RHEL/CentOS configuration of IPTABLES, traffic to the Gateway will be blocked unless action is taken to disable IPTABLES or to enable inbound traffic to the front-end protocol port(s).

• Gateway is not compatible with Linux PAM modules that depend on interactive validation operations such as OTP or biometric scanners.

• Gateway 8.0.4 must be restarted after creating a Search Feed to avoid the error: “ResourceUnavailableException: Application resource 'elasticsearch-storage_cluster' is unavailable”. This will be fixed in an upcoming release. (CLOUD-4003)

See Content Gateway 7 Release Notes and Content Gateway 6 Release Notes for known issues from prior releases that are still applicable, apart from those appearing above as fixed.