I’m currently experimenting with CircleCI to get our build running here instead of Travis, but I’m running into issues with ElasticSearch.
I’ve successfully set up the configuration for our script, and pretty much everything runs as expected, however at some point during the tests, our ElasticSearch keeps getting killed with error 137, which seems to be a memory issue.
Is there any support/way to configure ElasticSearch to work properly inside Docker?
I believe you are likely running out of memory. ElasticSearch is pretty heavy in that regard, you may need to submit a support ticket so we can take a look and investigate enabling
resource_class for your account.
yeah thanks for that
Currently talking our account maintainer to see if we can do this.
Actually got this resolved by limiting memory for ElasticSearch to just 256mb.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.