Transport client error after installing x-pack on es-5-5-1

[akshaymaniyar]

I have the following configs related to xpack:
xpack.security.enabled: false
xpack.monitoring.enabled: true
xpack.ml.enabled: false
xpack.graph.enabled: false
xpack.watcher.enabled: false

Also have the below:
node.ml: false

Still getting the below error. (Note Everything works as soon as I remove x-pack)

Caused by: java.lang.IllegalArgumentException: Unknown NamedWriteable [org.elasticsearch.cluster.metadata.MetaData$Custom][ml]
at org.elasticsearch.common.io.stream.NamedWriteableRegistry.getReader(NamedWriteableRegistry.java:112)
at org.elasticsearch.common.io.stream.NamedWriteableAwareStreamInput.readNamedWriteable(NamedWriteableAwareStreamInput.java:45)
at org.elasticsearch.common.io.stream.NamedWriteableAwareStreamInput.readNamedWriteable(NamedWriteableAwareStreamInput.java:39)
at org.elasticsearch.cluster.metadata.MetaData.readFrom(MetaData.java:682)
at org.elasticsearch.cluster.ClusterState.readFrom(ClusterState.java:659)
at org.elasticsearch.action.admin.cluster.state.ClusterStateResponse.readFrom(ClusterStateResponse.java:58)
at org.elasticsearch.transport.TcpTransport.handleResponse(TcpTransport.java:1428)
... 23 more

[TimV (Tim Vernum)]

Are you using the X-Pack transport client?

• https://www.elastic.co/guide/en/x-pack/5.5/java-clients.html

[dkyle (David Kyle)]

Machine Learning adds custom fields the the Elasticsearch metadata. From the stack trace I can see that ML has added its custom fields and so must have been enabled at some point. X-Pack knows how to parse the metadata and should be installed on every node. The X-Pack features don't have to be enabled but you must install X-Pack on every node in your cluster.

[akshaymaniyar]

Hi,

@Tim: Was not using the x-pack-transport client. I was using the org.elasticsearch.client:transport client. Was of the impression that x-pack-transport client is only required when security feature is being used. Since I had disabled the security feature, was using the normal transport client. The code is working perfectly after using the x-pack-transport client. Perhaps the same could be mentioned in the documentation that if you are using x-pack then always x-pack-transport client should be used. (Note this was not the case in es-5-2-2, normal transport client used to work with x-pack)

@dkyle: That explains why normal transport client used to work earlier and doesn't work now. FYI: X-pack was installed in all the machines. It seems just the normal transport client cannot be used now if you are using x-pack .

Thanks all!