laradock

1,998 Commits 1 Branch 159 Tags

3 Commits

Author	SHA1	Message	Date
ItaloBCandGitHub	bbbd247653	ElasticSearch instance fails at loading (wrong) ElasticSearch (ES from now onwards) will fail to initialize since the parameters for its environment are not correct or absent. These are: * `cluster.name`: Name of the cluster itself * `bootstrap.memory_lock`: Needed for ES to [lock the JVM into swap instead of memory](https://www.elastic.co/guide/en/elasticsearch/reference/master/_memory_lock_check.html). * `"ES_JAVA_OPTS=-Xms256m -Xmx256m"`: [Initial and maximum HEAP size for JVM](https://www.elastic.co/guide/en/elasticsearch/reference/current/_heap_size_check.html). Since it's locked to disk, should be the same. Half the defaults (512m) for development. * `ulimits: memlock: soft (-1), hard (-1)`: [ES needs to have unlimited access to memory](https://www.elastic.co/guide/en/elasticsearch/reference/current/max-size-virtual-memory-check.html), otherwise it will feel sluggish. * `mem_limit: 512m`: Hard limit the memory available for the container. This can, and should, be changed using `.env` file variables, but it seems that this should suffice for basic ES development.	2017-06-14 14:19:47 -04:00
ItaloBCandGitHub	03b551f9d6	Change to official repository Elastic.co announced they will pull out their official images from the Docker Registry and user their own. There will be no updates starting 6/20/2017. Pulling needs explicit version. Currently 5.4.1	2017-06-12 13:06:41 -04:00
ItaloBCandGitHub	30df311ec2	Change to official repository Elastic.co announced they will pull out their official images from the Docker Registry and user their own. There will be no updates starting 6/20/2017. Pulling needs explicit version. Currently 5.4.1	2017-06-12 13:02:08 -04:00

Author

SHA1

Message

Date

ItaloBCandGitHub

bbbd247653

ElasticSearch instance fails at loading (wrong)

ElasticSearch (ES from now onwards) will fail to initialize since the parameters for its environment are not correct or absent. These are:

* `cluster.name`: Name of the cluster itself
* `bootstrap.memory_lock`: Needed for ES to [lock the JVM into swap instead of memory](https://www.elastic.co/guide/en/elasticsearch/reference/master/_memory_lock_check.html).
* `"ES_JAVA_OPTS=-Xms256m -Xmx256m"`: [Initial and maximum HEAP size for JVM](https://www.elastic.co/guide/en/elasticsearch/reference/current/_heap_size_check.html). Since it's locked to disk, should be the same. Half the defaults (512m) for development.
* `ulimits: memlock: soft (-1), hard (-1)`: [ES needs to have unlimited access to memory](https://www.elastic.co/guide/en/elasticsearch/reference/current/max-size-virtual-memory-check.html), otherwise it will feel sluggish.  
* `mem_limit: 512m`: Hard limit the memory available for the container.

This can, and should, be changed using `.env` file variables, but it seems that this should suffice for basic ES development.

2017-06-14 14:19:47 -04:00

ItaloBCandGitHub

03b551f9d6

Change to official repository

Elastic.co announced they will pull out their official images from the Docker Registry and user their own. There will be no updates starting 6/20/2017.

Pulling needs explicit version. Currently 5.4.1

2017-06-12 13:06:41 -04:00

ItaloBCandGitHub

30df311ec2

Change to official repository

Elastic.co announced they will pull out their official images from the Docker Registry and user their own. There will be no updates starting 6/20/2017.

Pulling needs explicit version. Currently 5.4.1

2017-06-12 13:02:08 -04:00