Symptom: Quarkus fails at build time with Multiple extensions request different versions of Elasticsearch for Dev Services

[elvedins-monri]

I am developing a quarkus project as a part of a team, and we are using hibernatesearch to manage entities and to search the elasticsearch data. For a few features we need elasticsearch-java-client. But when I added the client dependency I started getting the exception from the title when I start the application in dev mode, or when running tests. It doesn't happen every time, but it occurs often enough that it fails our CI/CD pipeline when trying to run tests.

I found other discussions related to this issue, but none have helped to fix my problem.

I have tried every combination of properties to disable hibernatesearch devservices, and leave elasticsearch, and vice versa.

But whatever I try the exception happens.
In the latest iteration I tried disabling elasticsearch devservices completely, and run a dedicated elasticsearch container, but the exception still happens. I can't disable all devservices because we need them for postgresql and keycloak.

This is in my pom.xml:

`
<compiler-plugin.version>3.8.1</compiler-plugin.version>
<failsafe.useModulePath>false</failsafe.useModulePath>
<maven.compiler.release>17</maven.compiler.release>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
<quarkus.platform.artifact-id>quarkus-bom</quarkus.platform.artifact-id>
<quarkus.platform.group-id>io.quarkus.platform</quarkus.platform.group-id>
<quarkus.platform.version>3.0.4.Final</quarkus.platform.version>
<surefire-plugin.version>3.0.0-M7</surefire-plugin.version>

...

  <dependency>
  <groupId>io.quarkus</groupId>
  <artifactId>quarkus-elasticsearch-java-client</artifactId>
</dependency>


....

    <dependency>
  <groupId>io.quarkus</groupId>
  <artifactId>quarkus-hibernate-search-orm-elasticsearch</artifactId>
</dependency>

`
This is a part of the application.properties:

`
quarkus.elasticsearch.devservices.enabled=false

quarkus.elasticsearch.hosts=localhost:9200
%dev.quarkus.elasticsearch.hosts=localhost:9200

quarkus-elasticsearch-rest-client_quarkus-elasticsearch-connection-timeout=10s

#hibernate-search
quarkus.hibernate-search-orm.elasticsearch.version=8
%test.quarkus.hibernate-search-orm.elasticsearch.version=8
quarkus.hibernate-search-orm.elasticsearch.analysis.configurer=bean:myAnalysisConfigurer
%test.quarkus.hibernate-search-orm.schema-management.strategy=drop-and-create-and-drop
%dev.quarkus.hibernate-search-orm.schema-management.strategy=drop-and-create-and-drop
quarkus.hibernate-search-orm.schema-management.strategy=create-or-validate
quarkus.hibernate-search-orm.automatic-indexing.synchronization.strategy=sync
quarkus.hibernate-search-orm.elasticsearch.connection-timeout=10
quarkus.hibernate-search-orm.elasticsearch.read-timeout=120
quarkus.hibernate-search-orm.elasticsearch.request-timeout=120

%prod.hibernate-search-orm.elasticsearch.hosts=localhost:9200

`
Here is a part of the stack trace:

ERROR [io.qua.dep.dev.IsolatedDevModeMain] (main) Failed to start quarkus: java.lang.RuntimeException: io.quarkus.builder.BuildException: Build failure: Build failed due to errors ... Caused by: io.quarkus.builder.BuildException: Build failure: Multiple extensions request different versions of Elasticsearch for Dev Services. at io.quarkus.elasticsearch.restclient.common.deployment.DevServicesElasticsearchProcessor$DevservicesElasticsearchBuildItemsConfiguration.<init>(DevServicesElasticsearchProcessor.java:260)

During my investigation, I set a breakpoint in the DevServicesElasticsearchProcessor inside the
DevservicesElasticsearchBuildItemsConfiguration static class, and found out that the root cause appears to be two DevServices build items produced by different extensions:

• one for quarkus.elasticsearch.hosts with version=null and distribution=null
• one for quarkus.hibernate-search-orm.elasticsearch.hosts with version="8" and distribution=ELASTIC

and when it compares them the exception is thrown.
When the variable version is null, the exception is not thrown, but when it already has a value, and it compares the two it tries to compare version 8 to null.
I found out that by setting the property:
quarkus.hibernate-search-orm.elasticsearch.version=9,
I can alter the version of quarkus.hibernate-search-orm.elasticsearch.hosts value, but I can't change the value of
quarkus.elasticsearch.hosts. So it fails.

I have tried upgrading the project to version 3.9.5, and to 3.11.x. but the issue persists. And at the moment a version upgrade is the last option for our project, so I would like to find another avenue to fix this issue.

Can you help me with this?

[quarkus-bot[bot]]

/cc @geoand (devservices), @gsmet (elasticsearch), @holly-cummins (devservices), @loicmathieu (elasticsearch), @marko-bekhta (elasticsearch), @ozangunalp (devservices)

[marko-bekhta]

Hi @elvedins-monri 👋🏻 🙂

It is a current limitation reagarding the Elasticsearch devservices: there can only be one, and if multiple extensions request different versions, then there's the exception that you've encountered.
We are working on removing that limitation and allowing to have multiple Elasticseach services running (with any versions that the particular extensions request).
So with that in mind, changing to the newer version of Quarkus won't help for now.

It doesn't happen every time, but it occurs often enough that it fails our CI/CD pipeline when trying to run tests.

yeah 😔 looking at the way the checks are done in the DevservicesElasticsearchBuildItemsConfiguration the order in which you get the items matters, so that would explain the "randomness" of the failure.... 😕

Thanks for bringing this up! I'll send a patch for this later today.

[elvedins-monri]

Thank you for the quick response. I'm glad I could help. Looking forward to the patch