puppet-elasticsearch icon indicating copy to clipboard operation
puppet-elasticsearch copied to clipboard

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

Open gvenaas opened this issue 3 years ago • 2 comments

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.

gvenaas avatar Jun 18 '21 12:06 gvenaas

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.

nicky1038 avatar Apr 18 '23 21:04 nicky1038

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 :(

jplindquist avatar Aug 02 '23 23:08 jplindquist