Skip to content

support opensearch 3.x#73

Open
bugfood wants to merge 2 commits intovoxpupuli:masterfrom
bugfood:v3
Open

support opensearch 3.x#73
bugfood wants to merge 2 commits intovoxpupuli:masterfrom
bugfood:v3

Conversation

@bugfood
Copy link

@bugfood bugfood commented Feb 9, 2026

Pull Request (PR) description

Support opensearch 3.x.

This Pull Request (PR) fixes the following issues

Fixes #68

Notes and Caveats

This includes a change to the default config (remove gateway.recover_after_nodes) which affects earlier opensearch versions. Since the value removed is the default, there should be no net change, but this may trigger restarts, depending on the value of restart_on_config_change.

I have only put this in use enough to see that it seems to work. There may be some things for which I have failed to account.

I'm only working with opensearch 3.4, though I suspect other 3.x versions will work ok, since the changes are so minimal.

Installation via package only works on RHEL-based systems, not Debian-based systems. This is due to a pre-existing bug and is not specific to opensearch 3.x:
#55 which is actually an upstream bug; I commented on this here: opensearch-project/opensearch-build#5554 (comment)

Integration tests fail for the same reason as above.

Compare:
https://docs.opensearch.org/3.2/install-and-configure/configuring-opensearch/discovery-gateway-settings/
To:
https://docs.opensearch.org/3.3/install-and-configure/configuring-opensearch/discovery-gateway-settings/

gateway.recover_after_nodes is now gone, probably due to:
opensearch-project/OpenSearch#17357

The value of 0 here is documented to have been the default in 3.2 (and
presumably earlier versions).

This option may be replaceable by gateway.recover_after_data_nodes.
Don't configure that as a default within puppet-opensearch, though;
we don't need to mirror every upstream default here (indeed, the other
gateway options are already unspecified).
Note that security manager was deprecated in 3.0 and (apparently)
removed in at least 3.4.

https://opensearch.org/blog/finding-a-replacement-for-jsm-in-opensearch-3-0/

Enabling this in 3.4 gives the error:

    java.lang.Error: A command line option has attempted to allow or enable the Security Manager. Enabling a Security Manager is not supported.
@bugfood
Copy link
Author

bugfood commented Feb 10, 2026

The CI check failures are consistent with the pre-existing bug I mention above.

ERROR: Something went wrong during demo configuration installation. Please see the logs in /var/log/opensearch/install_demo_configuration.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Opensearch 3 support

1 participant