# IBM J9 and ES 2.4: I know it's not supported, but

**URL:** <https://discuss.elastic.co/t/ibm-j9-and-es-2-4-i-know-its-not-supported-but/169021>\
**Category:** Elasticsearch\
**Created:** [February 19, 2019, 12:34pm UTC](https://discuss.elastic.co/t/ibm-j9-and-es-2-4-i-know-its-not-supported-but/169021 "2019-02-19T12:34:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![miratim](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/miratim/32/41096_2.png) [@miratim](https://discuss.elastic.co/u/miratim)\
**Post date:** [February 19, 2019, 12:34pm UTC](https://discuss.elastic.co/t/ibm-j9-and-es-2-4-i-know-its-not-supported-but/169021/1 "2019-02-19T12:34:05Z")

</div>

Hi,

So we are using ES 2.4 (older version of our software in this case), and deploying on IBM J9. With the understanding that J9 is not supported by any ES version, we are seeing some strange things in a small 2 node embedded ES cluster:

1. A lot of chatter between the two ES nodes that we don't see in other environments; a lot of discovery messages going back and forth.
2. Client is reporting concerns about index corruption, although obviously we need to dig down into this.

Is anyone out there successfully using ES 2.4 (or higher) on IBM J9? Has anyone tried it? Are you seeing any problems, especially as described in #1/#2?

Thanks for inputs

---

<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:** [March 19, 2019, 12:34pm UTC](https://discuss.elastic.co/t/ibm-j9-and-es-2-4-i-know-its-not-supported-but/169021/2 "2019-03-19T12:34:11Z")

</div>

Closed on March 19, 2019, 12:34pm UTC

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