# Elastisearch requirements for OTRS 7 **URL:** \ **Category:** Elasticsearch\ **Created:** [May 17, 2019, 12:13pm UTC](https://discuss.elastic.co/t/elastisearch-requirements-for-otrs-7/181592 "2019-05-17T12:13:31Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![adbud866](https://avatars.discourse-cdn.com/v4/letter/a/bbce88/32.png) [@adbud866](https://discuss.elastic.co/u/adbud866)\ **Post date:** [May 17, 2019, 12:13pm UTC](https://discuss.elastic.co/t/elastisearch-requirements-for-otrs-7/181592/1 "2019-05-17T12:13:31Z")
Hello, I’m completely new to Elasticsearch but I need it for one of our applications and I hope I can get some recommendations on my query. I plan to install OTRS 7. OTRS uses Elasticsearch for its document search functionality. For the hardware requirements OTRS recommends using a machine with at least (that does not include Elasticsearch): • 3 GHz Xeon or comparable CPU • 8 GB RAM • 256 GB storage In our case that will be a VM running on VMware ESXi. In terms of Elasticsearch the requirements are: • Elasticsearch 6.x (higher versions are not supported) It can be installed on the same host as OTRS or on any remote host. I have collected some performance data over the last 30 days to provide an overview how “busy” the server is / or is not : `###CPU### 4 Core Intel(R) Xeon(R) Gold 6148 CPU @ 2.40GHz` ![cpu](https://us1.discourse-cdn.com/elastic/original/3X/d/f/dfb851d2699ffb7ecabcaa46412a4115ea8dc6c0.png) CPU wise there was not much going on. #MEMORY### 8 GB RAM ``` cat /proc/meminfo MemTotal: 7990288 kB MemFree: 3979288 kB MemAvailable: 4743564 kB Buffers: 1216 kB Cached: 790116 kB SwapCached: 0 kB Active: 2126240 kB Inactive: 1242976 kB Active(anon): 1699452 kB Inactive(anon): 923468 kB Active(file): 426788 kB Inactive(file): 319508 kB Unevictable: 0 kB Mlocked: 0 kB SwapTotal: 4194300 kB SwapFree: 4194300 kB Dirty: 40 kB Writeback: 0 kB AnonPages: 2577884 kB Mapped: 54216 kB Shmem: 45036 kB Slab: 431904 kB SReclaimable: 323788 kB SUnreclaim: 108116 kB KernelStack: 9680 kB PageTables: 23424 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 8189444 kB Committed_AS: 5073716 kB VmallocTotal: 34359738367 kB VmallocUsed: 198472 kB VmallocChunk: 34359310332 kB HardwareCorrupted: 0 kB AnonHugePages: 1241088 kB CmaTotal: 0 kB CmaFree: 0 kB HugePages_Total: 0 HugePages_Free: 0 HugePages_Rsvd: 0 HugePages_Surp: 0 Hugepagesize: 2048 kB DirectMap4k: 120640 kB DirectMap2M: 4073472 kB DirectMap1G: 6291456 kB ``` Memory usage on average is 26% with peeks up to 44%. ![memory](https://us1.discourse-cdn.com/elastic/original/3X/9/7/97126a1b860890882d3ec30bf4e5ea47ec16f3d1.png) Disk usage - not much to add: ![disk](https://us1.discourse-cdn.com/elastic/original/3X/a/8/a80497163e4fb272289bf50b973003a3ba18e14e.png) Here’s the DB size: `Database Size (0.629 GB) (MySQL 5.7.23)` Given the above what would be your recommendation: - How to scale the resource requirements to match OTRS and Elastisearch needs when installed on one VM? - Is there anything else to consider ? - Oh, and last but not least the LVM will be encrypted with `LUKS` does that make any difference to Elasticsearch ? I appreaciate all help in advance ! ---
**Author:** ![Igor\_Motov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_motov/32/45193_2.png) [@Igor\_Motov](https://discuss.elastic.co/u/Igor_Motov)\ **Post date:** [May 17, 2019, 9:10pm UTC](https://discuss.elastic.co/t/elastisearch-requirements-for-otrs-7/181592/2 "2019-05-17T21:10:14Z")
The system requirements for elasticsearch are very application-specific. I think you might get better answers if you ask this question on the [OTRS forum](https://forums.otterhub.org/) instead. ---
**Author:** ![adbud866](https://avatars.discourse-cdn.com/v4/letter/a/bbce88/32.png) [@adbud866](https://discuss.elastic.co/u/adbud866)\ **Post date:** [May 19, 2019, 6:54am UTC](https://discuss.elastic.co/t/elastisearch-requirements-for-otrs-7/181592/3 "2019-05-19T06:54:08Z")
Thank you @Igor_Motov Are there any other considerations / best practises to look at like 'do not install Elasticsearch on the same host running the application that hosts the data you want to ingest into Elasticsearch ? ---
**Author:** ![Igor\_Motov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_motov/32/45193_2.png) [@Igor\_Motov](https://discuss.elastic.co/u/Igor_Motov)\ **Post date:** [May 20, 2019, 5:28pm UTC](https://discuss.elastic.co/t/elastisearch-requirements-for-otrs-7/181592/4 "2019-05-20T17:28:32Z")
> [@adbud866](#): > > do not install Elasticsearch on the same host running the application that hosts the data you want to ingest into Elasticsearch ? It depends. In general we recommend a dedicated machine for elasticsearch since most of the defaults and setup recommendations are done assuming that all resources of the machine are devoted to elasticsearch. However, If you have a very small installation, and the application doesn't require a lot of resources, dedicating a separate machine to elasticsearch might not make any sense. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 17, 2019, 5:39pm UTC](https://discuss.elastic.co/t/elastisearch-requirements-for-otrs-7/181592/5 "2019-06-17T17:39:35Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.