Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
maxLevel2

...

  • Support for Elasticsearch 5.6 — This release of Content Gateway now completes support for Elasticsearch 5.6, so that you can finish the migration away from Elasticsearch 2.3.3 and reclaim those resources. With Gateway 6.0, your newly indexed Elasticsearch 5.6 feed will be made the primary search feed, which will include Swarm's new atime (access time) metadata for tracking content usage, if enabled. See Migrating from Older Elasticsearch.

  • Upgraded logging format — As part of support for Elasticsearch 5.6, the logging system for Content Gateway has been upgraded to log4j2, which offers more flexibility and hierarchical control. The configuration file, which was logging.cfg, is now logging.yamlSee Gateway Configuration. (CLOUD-3070)

  • Graceful reboots — Encryption keys are now persisted so that rebooting of the Gateway no longer disrupts active Swarm UI browser sessions. (CLOUD-3027)

  • Health reporting — The cluster health report that provides proactive support from Swarm now includes information about your Gateway installation, including its version and configured components. This feature requires valid entries for managementUser and managementPassword in the [storage_cluster] configuration section. See Gateway Configuration. (CLOUD-2753)

This release includes these fixes: 

  • The gateway error "Unable to create phone home data" was erroneously logged at startup. (CLOUD-3051)

  • A rare race condition could can result in a duplicate domain being created when enabling versioning in the Content UI. (CLOUD-3030)

  • After upgrading, the service might not automatically start after a system reboot. (CLOUD-2819)

  • The cloudgateway_server.log had invalid SCSP warnings reporting 'Failed requests will not be retried' and 'Failed querying cluster for name and version'. (CLOUD-2663)

  • When an EC write failed because of too few nodes to erasure-code a large object, S3 Gateway reported it as a failure to find the bucket. (CLOUD-1452)

Upgrade Impacts

Excerpt

Impacts for 6.0

  • Version Requirements

  • New logging — For Gateway system and audit logging, review the new, default logging.yaml file for any customizations that you may want to implement. See Gateway Configuration.

  • Buckets named "_admin" are no longer accessible via Gateway. If you have a legacy _admin bucket from csmeter, remove it with a DELETE request directly to Swarm. (CLOUD-3025)

...