Unknown xpack transport settings after upgrading to ES 6

[vb4t]

I am trying to upgrade one ES node to 6.0.0-beta1 (xpack 6 included). It do not start with following error message:

java.lang.IllegalArgumentException: unknown setting [transport.profiles.client.xpack.security.ssl.enabled] please check that any required plugins are installed, or check the breaking changes documentation for removed settings

There is also following WARN:

[xpack.security.transport.ssl.enabled] setting was deprecated in Elasticsearch and will be removed in a future release! See the breaking changes documentation for the next major version.

Both settings are described in documentation for X-Pack 6. So is it problem with outdated documentation or is it a bug in X-Pack? Which settings to use instead of these two?

[TimV (Tim Vernum)]

@vb4t

So is it problem with outdated documentation

Yes, the documentation for X-Pack security is not yet 100% up-to-date with the features in the beta.

For 6.0 we made TLS (SSL) mandatory for intra-cluster communication. That means that xpack.security.transport.ssl.enabled no longer has any effect. It is always enabled if X-Pack security is enabled.