Uses elasticsearch official image
ddev get ddev/ddev-elasticsearch
From within the container, the elasticsearch container is reached at hostname: "elasticsearch", port: 9200, so the server URL might be http://elasticsearch:9200
. You can also use the "ddev.site" http and https urls to access it: http://<projectname>.ddev.site:9200
, and https://<projectname>.ddev.site:9201
You can access the Elasticsearch server directly from the host for debugging purposes by visiting http://<projectname>.ddev.site:9200
. Via https you can access Elasticsearch via https://<projectname>.ddev.site:9201
This configuration limits memory usage to 512mb. This should be enough for most projects, but if your elasticsearch
service stops with no obvious reason, increase your docker max memory and/or the service max memory via the ES_JAVA_OPTS variable:
- "ES_JAVA_OPTS=-Xms512m -Xmx512m"` environment variable in `docker-compose.elasticsearch.yaml`
If you change this variable, make sure to remove the #ddev-generated
line at the top of the file.
You can use ddev logs -s elasticsearch
to investigate what the elasticsearch daemon has been up to, or if you have a RAM-related crash.
- There are two related answers to the Stack Overflow question on ddev and Elasticsearch.
- @juampynr's Lullabot article on Drupal 8 and Elasticsearch is helpful for Drupal users.
Originally Contributed by dacostafilipe with contributions by @Morgy93, @amitaibu, @aronnovak and others
Maintained by @aronnovak