If the issue is the search index configuration, there are a few additional suggestions for checking and troubleshooting Elasticsearch on this page:
Can you try running the search:status task and checking cluster health, and share the results with us?
Additionally, how much RAM does your AtoM server have? Many Elasticsearch issues are caused by a lack of memory. As noted in our Requirements documentation
, we recommend the following as target minimums for a production-ready environment:
- Processor: 2 vCPUs @ 2.3GHz
- Memory: 7GB
- Disk space (processing): 50GB at a minimum for AtoM’s core stack plus more storage would be required for supporting any substantial number of digital objects.
I would suggest that for a production installation, 4GB RAM would be on the lower end, and 2GB would be the absolute lowest value for a very small installation. You may still experience issues with that little RAM, as Elasticsearch will need at least half of it.
In some cases (such as this forum thread
), we have heard of users having enough general memory on the server, but not enough available to Elasticsearch - particularly, the Java Virtual Machine (JVM)'s heap_size value. JVM is an Elasticsearch dependency, and the heap size is the amount of RAM allocated to the Java Virtual Machine of an Elasticsearch node, which is configured by setting -Xms
values. I believe the default value at installation for the heap size is 1GB. If your AtoM server has 4GB RAM or more but you're still having problems and none of the above suggestions have helped, then you might want to try increasing the heap size to 2GB. As a general rule, you should set -Xms
to the SAME value, which should be 50% of your total available RAM. A higher heap size will give your node more memory for indexing and search operations. However, your node also requires memory for caching, so using 50% maintains a healthy balance between the two.
For some further information and suggestions on this, including how to increase the JVM heap size, see:
Let us know what you find!