-
Notifications
You must be signed in to change notification settings - Fork 25
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
ELASTICSEARCH_ENDPOINT not working in Docker Standalone (cassproject/cass) #228
Comments
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 |
@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. |
@miledivovic going back to version |
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. |
Let's strip environment variables from the pm2 files, especially when they match the defaults.
|
Additionally, the upgrade to 8.23 shouldn't require any database upgrades. Just API changes. |
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.
The text was updated successfully, but these errors were encountered: