Bug 1387307

Summary:	Cassandra crash at startup using amazon EFS as NFS
Product:	OpenShift Container Platform	Reporter:	Brendan Mchugh <bmchugh>
Component:	Storage	Assignee:	Matthew Wong <mawong>
Status:	CLOSED NOTABUG	QA Contact:	Jianwei Hou <jhou>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.3.0	CC:	aos-bugs, bchilds
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-10-27 22:08:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Comment 3 Matthew Wong 2016-10-27 20:07:01 UTC

I found it's a bug with Java, nothing to do with openshift. http://mail.openjdk.java.net/pipermail/nio-dev/2016-July/003784.html https://bugs.openjdk.java.net/browse/JDK-8162520

Basically my understanding is: cassandra calls this Java 'Files.getFileStore' function as part of its check to see how much disk space to use for its "commitlog". Amazon EFS reports 8 exabytes (I guess because it's scalable and has lots of fancy non-standard features?) which overflows the int and causes the 'java.lang.IllegalArgumentException: Out of range: -2199023255552' that the bug reporter sees

So this would have to be fixed in JDK, or addressed by cassandra or EFS.

Comment 4 Bradley Childs 2016-10-27 22:08:53 UTC

This is a bug on the java/cassandra side of things based on EFS disk size reporting.  Closing as not-a-bug per Mathew's comments.