Elasticsearch breaking changes
editElasticsearch breaking changes
editThis list summarizes the most important breaking changes in Elasticsearch 7.15.2. For the complete list, go to Elasticsearch breaking changes.
Security changes
editThe xpack.security.transport.ssl.enabled
setting will be required to configure xpack.security.transport.ssl
settings.
Details
Configuring any SSL settings for
xpack.security.transport.ssl
without also configuring
xpack.security.transport.ssl.enabled
generates warnings in the deprecation
log. In 8.0, this configuration will result in errors.
Impact
To avoid deprecation warnings, either:
-
Explicitly set
xpack.security.transport.ssl.enabled
asfalse
-
Discontinue use of other
xpack.security.transport.ssl
settings
If you want to enable SSL, follow the instructions to
encrypt internode communications with TLS. As part of this configuration, explicitly set
xpack.security.transport.ssl.enabled
as true
.
For example:
The xpack.security.http.ssl.enabled
setting will be required to configure xpack.security.http.ssl
settings.
Details
Configuring any SSL settings for xpack.security.http.ssl
without also
configuring xpack.security.http.ssl.enabled
generates warnings in the
deprecation log. In 8.0, this configuration will result in errors.
Impact
To avoid deprecation warnings, either:
-
Explicitly set
xpack.security.http.ssl.enabled
asfalse
-
Discontinue use of other
xpack.security.http.ssl
settings
If you want to enable SSL, follow the instructions to
encrypt HTTP client communications for Elasticsearch. As part
of this configuration, explicitly set xpack.security.http.ssl.enabled
as true
.
For example:
A xpack.security.transport.ssl
certificate and key will be required to enable SSL for the transport interface.
Details
Enabling SSL for the transport interface without also configuring a certificate
and key through use of the xpack.security.transport.ssl.keystore.path
setting or the xpack.security.transport.ssl.certificate
and
xpack.security.transport.ssl.key
settings generates warnings in the
deprecation log. In 8.0, this configuration will result in errors.
Impact
If xpack.security.transport.ssl.enabled
is set to true
, provide a
certificate and key using the xpack.security.transport.ssl.keystore.path
setting or the xpack.security.transport.ssl.certificate
and
xpack.security.transport.ssl.key
settings. If a certificate and key is not
provided, Elasticsearch will generate warnings in the deprecation log.
A xpack.security.http.ssl
certificate and key will be required to enable SSL for the HTTP layer.
Details
Enabling SSL for the HTTP layer without also configuring a certificate and key
through use of the xpack.security.http.ssl.keystore.path
setting or
the xpack.security.http.ssl.certificate
and xpack.security.http.ssl.key
settings generates warnings in the deprecation log. In 8.0, this configuration
will result in errors.
Impact
If xpack.security.http.ssl.enabled
is set to true
, provide a
certificate and key using the xpack.security.http.ssl.keystore.path
setting or the xpack.security.http.ssl.certificate
and
xpack.security.http.ssl.key
settings. If a certificate and key is not
provided, Elasticsearch will generate warnings in the deprecation log.
Indices deprecations
editIndices created in Elasticsearch 6.x and earlier versions are deprecated.
Details
In 8.x, Elasticsearch will only read indices created in version 7.0 or above. An 8.x node
will not start in the presence of indices created in 6.x or earlier versions of
Elasticsearch.
Impact
Before upgrading to an 8.x version, reindex any index created in 6.x or earlier
versions with Elasticsearch 7.x. If you no longer need the index, delete it instead.
You can use the get index API to check the Elasticsearch version in which an index
was created.
GET *,-.*?human=true&filter_path=**.settings.index.version.created_string
The simpleifs
index store type is deprecated.
Details
The simplefs
value for the index.store.type
index setting is now deprecated. Use the niofs
value for superior or
equivalent performance instead.
Impact
To avoid deprecation warnings, discontinue use of the simpleifs
store type in
new indices or index templates. Reindex any index using simplefs
into one with
another store type.
Security deprecations
editThe accept_default_password
setting is deprecated.
Details
In 6.0, we deprecated the accept_default_password
cluster setting. We removed
support for default passwords in 6.0 but did not remove the setting for
backwards compatibility. In 8.0, we will remove the setting.
Impact
To avoid deprecation warnings, discontinue use of the setting.
Native role cache settings are deprecated.
Details
In 5.2, we deprecated the following cluster settings:
-
xpack.security.authz.store.roles.index.cache.max_size
-
xpack.security.authz.store.roles.index.cache.ttl
These native role cache settings have been unused since 5.2, but we did not remove the settings for backwards compatibility. In 8.0, we will remove the settings.
Impact
To avoid deprecation warnings, discontinue use of the settings.
Settings deprecations
editFractional byte size values are deprecated.
Details
In 6.2, we deprecated support for fractional byte size values, such as 23.5pb
,
in:
- Cluster settings
- Index settings
- Cluster state metadata, such as an ILM policy, that support byte size values
Impact
To avoid deprecation warnings, discontinue use of fractional byte size values in
your configurations. Update any existing configurations to use whole values.