Making an upgrade without ElasticSearch

I'm trying to upgrade a Sugar instance from 7.5 to 7.7 but for the moment ElasticSearch service isn't available on our server. This cause that the upgrade can't execute as expected. The message "Couldn't connect to host. Elasticsearch down?" repeats every time I tried to did it.

Is there any way to make an upgrade if ElasticSearch service isn't running properly?

Angel's approach would be a great stop-gap solution. Create a simple Virtual Machine and install Elastic Search. Point Sugar to that just so that it will upgrade and function while your IT department builds out a proper Elastic Search installation. Installing and configuring Elastic Search is pretty easy on a Linux stack as it's now in most debian and rpm repositories.

Upgrade would fail anyway due to Elasticsearch. If its on your local, i would recommend you to install elasticsearch and set it up as its. But if it's on cloud then i would recommend you to get your backup to your local then install your elasticsearch to your local and proceed the upgrade. Once you done you can upload the upgraded version to your cloud.

I know ElasticSearch it's required component for install or upgrade Sugar, and for that it will be available in a few weeks. But now, I would like to save valuable time finishing the upgrade to make some test with my environment.

I know that is not part of the best practices, but what if I force the script of the "pre" step that makes the validation of FTS connection?. I can hardcode and return "true" value in the function that makes the validation to pass the "pre" step.

Wouldn't it be easier to install ES on a test machine (or yours) and then simply configure the Sugar instance to use that instance of ES for the upgrade?

Once the upgrade is complete, you can then configure Sugar to use the proper ES server and rebuild the index. You are not going to lose any data in the process as ES isn't Sugar's main datastore. Whether that happens immediately after the upgrade or weeks later is somewhat irrelevant.

I perfectly understand your approach. But unfortunately there isn't easy way to skip over Elasticsearch in the upgrade progress. As far as i know elasticsearch isn't used in only one place. There are multiple places we check elasticsearch and we actually use it (especially for upgrade). So even if you skip in the pre check you might bump in the middle of progress.

Like i mentioned in my first note, it would highly recommend you to have your backup to your local test machine.

Angel's approach would be a great stop-gap solution. Create a simple Virtual Machine and install Elastic Search. Point Sugar to that just so that it will upgrade and function while your IT department builds out a proper Elastic Search installation. Installing and configuring Elastic Search is pretty easy on a Linux stack as it's now in most debian and rpm repositories.

Like Jason said, one approach would be to use Virtual Machine, or even easier might be to use docker containers. There is official docker image that you can use(note that you will need to use branch 1.4):