# Running ELK stack on a server with Websphere and JBoss application servers

**URL:** <https://discuss.elastic.co/t/running-elk-stack-on-a-server-with-websphere-and-jboss-application-servers/106408>\
**Category:** Elasticsearch\
**Created:** [November 5, 2017, 8:42am UTC](https://discuss.elastic.co/t/running-elk-stack-on-a-server-with-websphere-and-jboss-application-servers/106408 "2017-11-05T08:42:38Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ihjaz](https://avatars.discourse-cdn.com/v4/letter/i/8baadc/32.png) [@Ihjaz](https://discuss.elastic.co/u/Ihjaz)\
**Post date:** [November 5, 2017, 8:42am UTC](https://discuss.elastic.co/t/running-elk-stack-on-a-server-with-websphere-and-jboss-application-servers/106408/1 "2017-11-05T08:42:38Z")

</div>

Hi,

I'm planning to install ELK stack on nodes which also has a Websphere and a JBoss application server running. There will be multiple applications running on Websphere and 40% of the system's RAM is going to be allocated to that.

I read that Lucene may take up the remaining RAM that is left on the system.

Is this kind of ELK deployment OK to have ?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 5, 2017, 8:48am UTC](https://discuss.elastic.co/t/running-elk-stack-on-a-server-with-websphere-and-jboss-application-servers/106408/2 "2017-11-05T08:48:33Z")

</div>

FYI we’ve renamed ELK to the Elastic Stack, otherwise Beats and APM feel left out! 😉

> [@Ihjaz](#):
>
> I read that Lucene may take up the remaining RAM that is left on the system.

The OS may cache files that Lucene reads, not Lucene itself.

> [@Ihjaz](#):
>
> Is this kind of ELK deployment OK to have ?

It should be fine. Again, it's the OS that handles this 🙂

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [November 5, 2017, 9:34am UTC](https://discuss.elastic.co/t/running-elk-stack-on-a-server-with-websphere-and-jboss-application-servers/106408/3 "2017-11-05T09:34:34Z")

</div>

But remember that your applications will steal some CPU resources. Ideally having an external elasticsearch cluster is better but as Mark said this can work well depending on the overall load.

---

<div class="post-metadata">

**Author:** ![Ihjaz](https://avatars.discourse-cdn.com/v4/letter/i/8baadc/32.png) [@Ihjaz](https://discuss.elastic.co/u/Ihjaz)\
**Post date:** [November 5, 2017, 9:46am UTC](https://discuss.elastic.co/t/running-elk-stack-on-a-server-with-websphere-and-jboss-application-servers/106408/4 "2017-11-05T09:46:07Z")

</div>

Thanks @warkolm and @dadoonet for quick replies.

I had a related question. I see that Elasticsearch JVM heap size is set to 2 GB by default. My log searches are going to be very minimal. So is it OK to reduce the JVM size of Elasticsearch to 1 GB or less in order to give more RAM for other applications.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [November 5, 2017, 9:58am UTC](https://discuss.elastic.co/t/running-elk-stack-on-a-server-with-websphere-and-jboss-application-servers/106408/5 "2017-11-05T09:58:33Z")

</div>

It can work. I'd probably never go under 1gb though.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 3, 2017, 10:09am UTC](https://discuss.elastic.co/t/running-elk-stack-on-a-server-with-websphere-and-jboss-application-servers/106408/6 "2017-12-03T10:09:00Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
