chore(clouseau): bump to 3.0.0
#5794
Merged
+262
−116
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nickva
approved these changes
Nov 30, 2025
Chase the release of the brand new 3.0.0 version of Clouseau aka. ZIOSE (ZIO "Search Engine") and make it the default onwards. While this is a drop-in replacement for 2.x, note that it is based on completely different foundation, libraries and build system, as well as Java 21 and G1 as the default garbage collector -- update the `dev/run` script to make it work with both 2.x and 3.x in response to that. This warrants that Clouseau 2.x will keep working from both binary and source, albeit it has now been deprecated.
Even though the build environments implictly configure the Java location that is specific to Clouseau via environment variables, it makes sense to make it possible for the developers to redefine the respective paths ad hoc. When upgrading to 3.x, it can even help with rerolling the container images only after the switch and avoid breaking the CI that may still run with Clouseau 2.x. Later this may become equally beneficial if the required Java versions are different from what other dependencies, e.g. Nouveau assume.
The Erlang cookie shared by the CouchDB and Clouseau nodes goes out of sync somehow mysteriously which makes the corresponding tests fail immediately. Until the exact causes are known, work around this issue by configuring both sides with the same string (via the `ERLANG_COOKIE` make variable) and do not rely on other implicit methods of generating and obtaining the cookie from other sources.
For some reason, the local cluster to run the integration tests that may require Clouseau (Search) does not always start up properly which makes the execution hang indefinitely when run in a Docker container. Work around the issue by setting a reasonable time limit (5 minutes) for each of those and combined with the Jenkins retry, it can help with recovering the build in such unfortunate scenarios.
pgj
force-pushed
the
jenkins-clouseau-3.0.0
branch
from
2de78d7 to
f3e3928
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Chase the release of the brand new 3.0.0 version of Clouseau aka. ZIOSE (ZIO "Search Engine") and make it the default onwards. While this is a drop-in replacement for 2.x, note that it is based on completely different foundation, libraries and build system, as well as Java 21 and G1 as the default garbage collector — update the
dev/runscript to make it work with both 2.x and 3.x in response to that.This warrants that Clouseau 2.x will keep working from both binary and source, albeit it has now been deprecated.
Thanks @iilyak @jiahuili430 @jaydoane for making this happen!
Testing recommendations
Other than exercising the change in the CI, one could manually verify it. Configure with Clouseau enabled (UNIX-like systems, including macOS) and be sure to have Java 21 on the path:
or on Windows:
.\configure.ps1 -WithClouseauNote that you may have to remove any older local installation of Clouseau before proceeding:
Run the Mango tests (implies using Clouseau):
Note that there shall be only a single skipped test in this scenario. Anything more than that may signal that Clouseau has not been fully configured.
Run the Elixir search tests (implies using Clouseau):
This should all work with Erlang/OTP 26, 27, or later.
To verify if logging is still working, you can take a look at the contents of the
dev/logs/clouseau1.logfile after Clouseau has been started up alongside CouchDB, e.g.:Checklist