# Elasticsearch transform role backward compatibility

**URL:** <https://discuss.elastic.co/t/elasticsearch-transform-role-backward-compatibility/259254>\
**Category:** Elasticsearch\
**Created:** [December 21, 2020, 1:07pm UTC](https://discuss.elastic.co/t/elasticsearch-transform-role-backward-compatibility/259254 "2020-12-21T13:07:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mohammad\_Mousavi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mohammad_mousavi/32/56508_2.png) [@Mohammad\_Mousavi](https://discuss.elastic.co/u/Mohammad_Mousavi)\
**Post date:** [December 21, 2020, 1:07pm UTC](https://discuss.elastic.co/t/elasticsearch-transform-role-backward-compatibility/259254/1 "2020-12-21T13:07:24Z")

</div>

Hi, I have a 3 nodes elasticsearch cluster with 7.4.2 version.  
It's look like this version does not support "transform role". I see in elasticsearch version 7.10.1 logs that a module called "transform" is loaded in starting elasticsearch service. It's look like it does not exist in version 7.4.2 .  
This is version 7.4.2 with node role transfoem in config file:

`org.elasticsearch.bootstrap.StartupException: java.lang.IllegalArgumentException: unknown setting [node.roles] please check that any required plugins are installed, or check the breaking changes documentation for removed settings`

I've setup a 4th node with version 7.10.1 and join this new node to cluster with transform role ( I know it's stupid but I just wanted to test )  
I've tested kibana version 7.10.1 and it can not connect to elasticsearch version 7.4.2 .  
The \_transform api also does not work properly.  
Upgrading my cluster will cost me a lost. It will be the last option.  
Is there any way to use "transform role" in elasticsearch and kibana version 7.4.2 ??  
I don't know , maybe with install some plugin or modules or what ever.  
Sorry for my poor English.  
Thanx a lot.

---

<div class="post-metadata">

**Author:** ![Hendrik\_Muhs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hendrik_muhs/32/25802_2.png) [@Hendrik\_Muhs](https://discuss.elastic.co/u/Hendrik_Muhs)\
**Post date:** [December 21, 2020, 1:36pm UTC](https://discuss.elastic.co/t/elasticsearch-transform-role-backward-compatibility/259254/2 "2020-12-21T13:36:16Z")

</div>

A cluster must always be formed from the same version, if you want to add a new node to an existing cluster it _must_ be the same minor (you can add a node with a newer patch revision (the last digit, e.g. 7.4.3 - if 7.4.3 would exist).

The only valid case for a so called mixed version cluster is during a rolling upgrade. That brings me to:

> Upgrading my cluster will cost me a lost.

Upgrades can be done in a rolling fashion _without_ downtime, see [Rolling upgrade | Elasticsearch Guide [8.11] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/rolling-upgrades.html)

The problems you see with transform is just the tip of the iceberg, using a much newer kibana version with an old elasticsearch cluster is not supported.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 18, 2021, 1:36pm UTC](https://discuss.elastic.co/t/elasticsearch-transform-role-backward-compatibility/259254/3 "2021-01-18T13:36:21Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.