ELASTICSEARCH_ENDPOINT not working in Docker Standalone (cassproject/cass)

[FunkMonkey]

The server always uses http://localhost:9200, because the environment variable is overwritten by pm2.standalone.config.js.

The values in the docker-compose.yml are thus also unused.

[FunkMonkey]

Maybe this is connected to version 1.5.10 standalone simply not working at all. It keeps waiting for elasticsearch, which is why I assumed I must be able to setup my own elasticsearch instance, but looking at #223 it seems, that the normal standalone variant should already startup its own elasticsearch, so http://localhost:9200 should always be fine there

[miledivovic]

@FunkMonkey I've experienced something similar in the past, if elasticsearch doesn't have enough resources to start (RAM/storage) it just silently fails and CASS ends up waiting indefinitely.

[FunkMonkey]

@miledivovic going back to version 1.5.6 fixed this problem for me, so I don't think it has anything to do with resources

[gloverkari]

This might also be related to the elasticsearch upgrade. If on a version earlier than 7.17, then Elasticsearch needs to upgrade to 7.17 before upgrading to 8.23. To do so, set the version to 7.17 in docker-compose, let it upgrade, and then set to 8.23.

[Lomilar]

Let's strip environment variables from the pm2 files, especially when they match the defaults.

• Strip environment variables from the pm2 files, especially when they match the defaults.

[Lomilar]

Additionally, the upgrade to 8.23 shouldn't require any database upgrades. Just API changes.