# Nexus 3 on docker on nfs4 (efs) reports highwatermark

**URL:** <https://discuss.elastic.co/t/nexus-3-on-docker-on-nfs4-efs-reports-highwatermark/62361>\
**Category:** Elasticsearch\
**Created:** [October 6, 2016, 10:45am UTC](https://discuss.elastic.co/t/nexus-3-on-docker-on-nfs4-efs-reports-highwatermark/62361 "2016-10-06T10:45:43Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![lsilva](https://avatars.discourse-cdn.com/v4/letter/l/73ab20/32.png) [@lsilva](https://discuss.elastic.co/u/lsilva)\
**Post date:** [October 6, 2016, 10:45am UTC](https://discuss.elastic.co/t/nexus-3-on-docker-on-nfs4-efs-reports-highwatermark/62361/1 "2016-10-06T10:45:43Z")

</div>

Hi,

I installed nexus3 opensource (which uses ES 2.2) using the sonatype docker container. The underlying filesystem is nfsv4 (Amazon EFS) mounted at /nexus-data on the container.

When I start the nexus container, elasticsearch complains with an error:  
\*SYSTEM org.elasticsearch.cluster.routing.allocation.decider - [....] high disk watermark [90%] exceeded on [.....][/nexus-data/elasticsearch/nexus/nodes/0] **free: 8191.9pb[-99.9%],** shards will be relocated away from this node

Both the host OS and the container correctly report disk space, but ES interprets it as a negative value (some kind of overflow?).

If I disable watermark checks with "cluster.routing.allocation.disk.threshold\_enabled: false" I get no more errors and es and nexus work fine, but I wonder what else might break if ES disk information is broken.

See the details below. Any help is appreciated.

**Disk space reported inside container**

$ df -t nfs4  
Filesystem 1K-blocks Used Available Use% Mounted on  
REDACTED\_EFS\_ENDPOINT:/ 9007199254740992 107520 9007199254633472 1% /nexus-data

**Cutdown report of \_node/stats**

"fs": {  
"timestamp": 1475748403553,  
"total": {  
"total\_in\_bytes": \*\*-\*\*9223372036854775808,  
"free\_in\_bytes": 9223372036744675328,  
"available\_in\_bytes": 9223372036744675328,  
"spins": "true"  
},  
"data": [{  
"path": "/nexus-data/elasticsearch/nexus/nodes/0",  
"mount": "/nexus-data ([eu-west-1c.fs-276294ee.efs.eu-west-1.amazonaws.com](http://eu-west-1c.fs-276294ee.efs.eu-west-1.amazonaws.com):/)",  
"type": "nfs4",  
"total\_in\_bytes": \*\*-\*\*9223372036854775808,  
"free\_in\_bytes": 9223372036744675328,  
"available\_in\_bytes": 9223372036744675328,  
"spins": "true"  
}]  
},

**Elasticsearch details**

{  
"name" : "....",  
"cluster\_name" : "nexus",  
"version" : {  
"number" : "2.2.0",  
"build\_hash" : "NA",  
"build\_timestamp" : "NA",  
"build\_snapshot" : false,  
"lucene\_version" : "5.4.1"  
},  
"tagline" : "You Know, for Search"  
}

---

<div class="post-metadata">

**Author:** ![ywelsch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ywelsch/32/7751_2.png) [@ywelsch](https://discuss.elastic.co/u/ywelsch)\
**Post date:** [October 6, 2016, 11:52am UTC](https://discuss.elastic.co/t/nexus-3-on-docker-on-nfs4-efs-reports-highwatermark/62361/2 "2016-10-06T11:52:17Z")

</div>

seems to be a duplicate of [Elasticsearch with Amazon Elastic File System](https://discuss.elastic.co/t/elasticsearch-with-amazon-elastic-file-system/55867/9)

It is fixed in 2.4.1 [https://github.com/elastic/elasticsearch/pull/20527](https://github.com/elastic/elasticsearch/pull/20527) and caused by a bug in the JDK: [https://bugs.openjdk.java.net/browse/JDK-8162520:](https://bugs.openjdk.java.net/browse/JDK-8162520:)

Can you verify that 2.4.1 works for you?

---

<div class="post-metadata">

**Author:** ![lsilva](https://avatars.discourse-cdn.com/v4/letter/l/73ab20/32.png) [@lsilva](https://discuss.elastic.co/u/lsilva)\
**Post date:** [October 6, 2016, 1:58pm UTC](https://discuss.elastic.co/t/nexus-3-on-docker-on-nfs4-efs-reports-highwatermark/62361/3 "2016-10-06T13:58:09Z")

</div>

Thank you, they are indeed the same.

I can't use ES 2.4.1 since the ES OSGI bundle is created by sonatype and also dependant on apache.servicemix to create a bundle for ES 2.4.1.

I've opened a bug with Sonatype to see if they can upgrade to 2.4.1 with their next release.

Thanks for the swift response!

---

<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:** [July 5, 2017, 10:14pm UTC](https://discuss.elastic.co/t/nexus-3-on-docker-on-nfs4-efs-reports-highwatermark/62361/4 "2017-07-05T22:14:15Z")

</div>