# WARN in Logs: "cannot compute used memory / swap"
**URL:** https://discuss.elastic.co/t/warn-in-logs-cannot-compute-used-memory-swap/244417
**Category:** Elasticsearch
**Created:** [August 10, 2020, 2:26pm UTC](https://discuss.elastic.co/t/warn-in-logs-cannot-compute-used-memory-swap/244417 "2020-08-10T14:26:30Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@mfloryan](https://discuss.elastic.co/u/mfloryan)
#### Post date: [August 10, 2020, 2:26pm UTC](https://discuss.elastic.co/t/warn-in-logs-cannot-compute-used-memory-swap/244417/1 "2020-08-10T14:26:31Z")
Elasticsearch 7.8.1 installed on Debian 10 (buster) running on an OpenVZ host. It's a fresh install and the server has 8GB of memory.
The logs are getting filled with the following two entires:
> cannot compute used memory when total memory is 0 and free memory is 5992394752
> cannot compute used swap when total swap is 0 and free swap is 268435456
I wonder if anyone else bumped into similar problem.
---
### Author:  [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [August 10, 2020, 3:19pm UTC](https://discuss.elastic.co/t/warn-in-logs-cannot-compute-used-memory-swap/244417/2 "2020-08-10T15:19:59Z")
These warnings are spurious, related to a JDK-14 bug, see [https://github.com/elastic/elasticsearch/pull/60375](https://github.com/elastic/elasticsearch/pull/60375) for details and the fix. The fix isn't released yet, so for now you should just ignore these warnings.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [September 7, 2020, 3:20pm UTC](https://discuss.elastic.co/t/warn-in-logs-cannot-compute-used-memory-swap/244417/3 "2020-09-07T15:20:01Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.