Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade path from 6.x (Multi instance) to 7.x + (Single instance #1120

Open
gvenaas opened this issue Jun 18, 2021 · 2 comments
Open

Upgrade path from 6.x (Multi instance) to 7.x + (Single instance #1120

gvenaas opened this issue Jun 18, 2021 · 2 comments

Comments

@gvenaas
Copy link

gvenaas commented Jun 18, 2021

Feature Description

As described in the module description:

"Therefore in-place upgrades from version 6.x of this module to 7.x, or migrations from multi-instance to single deployment is not currently supported.

We hope to add support for this in a future release."

Its been some time since the 7 support was released.

Could You comment on when You think an upgrade path will be provided.

@nicky1038
Copy link

First of all, I would like to thank all the maintainers of this package for that they've ever made a lot of effort for its creation, so that a lot of users have opportunity to deploy their Elasticsearch instances with Puppet.

But also with that, I am very confused with their decision of dropping multi-instance support in v7 of the package. I believe that my feelings have already been expressed by a lot of people many times over the years, nevertheless, I'll say it once again. Multi-instance configuration is still being supported in Elasticsearch itself, so, logically, end of its support in this Puppet package should not have happened. This decision has affected everyone with such a deployment type, making all these people find out how to fix what has always been worked and should have continued working well. The choice was made for them: either not upgrading from v6 (which becomes way too old), or not using multi-instance setup, or not using this package at all, in favor of Docker or some other workarounds.

I also ask the maintainers to help all those people, who used/still use multi-instance ES by whatever reason, and return the absent functionality back. Thank you.

@jplindquist
Copy link

This was the "recommended" method a few years ago in order to maximise the memory utilisation for a given host containing more than 32GB of RAM. However other methods have become more prevalent since, such as running Elasticsearch in Docker.

ref #1068

Maybe we're in the minority here, but there are other installation methods besides for docker, especially when we've got some beefy hardware instead of adding another unnecessary layer. I see others asking for the same thing, but I would also love to see support for multiple instances come back. The removalhas left us in a bind with being unable to keep updated with this module, and leaving us in a forked state for now :(

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

No branches or pull requests

3 participants