enaio® fulltext

enaio® 10.10 »

enaio® fulltext is based on the add-on software Elasticsearch. You estimate the size of the full-text database as follows:

25 to 30 GB HDD will be needed for roughly one million objects in the database (depending on document content and diversity). An additional 25 to 30 GB is required per replica. Replicas must be used in cluster installations (more than one Elasticsearch node). They are used to ensure data availability as well as the performance and hence scalability of enaio® fulltext.

The Elasticsearch database cannot be on \\UNC paths\ or on connected network drives. It must be located locally. Elasticsearch is always a cluster with at least one node. It is recommended that you always select an odd number of nodes when scaling Elasticsearch.

Scaling is recommended once the size of the database on the HDD (without replicas) exceeds the RAM available to Elasticsearch by a factor of ten. At this point, the cluster should be extended with max. 64 GB RAM per Elasticsearch node.

Working in the database places relatively high demands of HDD resources. It is not necessary to use SSD premium storage memory. Follow this general rule of thumb: The less RAM is available, the faster the HDD needs to be in order to keep pace with contents from the database.