Impacts for 9.0ES Migration Check - Elasticsearch 2.x has many breaking changes. In particular, if a custom metadata field name includes a period/dot (x-sample-meta-bad.field.name), your existing data cannot be upgraded. Elasticsearch recommends running the migration plugin to check for problems: Install the migration checker: https://github.com/elastic/elasticsearch-migration/tree/1.x Browse to http://{Elasticsearch-domain-endpoint}/_plugin/migration/ Select Run checks now. If problems are found, work with DataCore Support to fix your data.
Deprecated and Removed Settings - Remove these settings from your configuration files and use any new settings specified. See Replaced Settings. cluster.proxyPort cluster.proxyIPAddress cluster.settingsUuid disk.automaticFormat security.noauth
Deprecated: The native Swarm auth/auth feature is deprecated and is removed as of June 2017. If you are using Swarm's native auth/auth for your applications, you must add security.noauth = False now in order to continue using the native auth/auth. During a rolling upgrade, you may see SCSP errors on the target cluster ("Castor-System-Cluster value must refer to a remote cluster on RETRIEVE request"); these are harmless and stop when the cluster upgrade is complete. (SWAR-7038) Upgrading from 8.0 replaces several EC and replication settings with the new policy settings. Should you boot an 8.0 node before completing a rolling upgrade to or downgrade from 8.1 or 8.2 (and so have mixed nodes), the new policy settings are removed from the persisted settings and need to be restored using SNMP. See Persisted Settings (SNMP). (SWAR-6901)
|
