Bug 1387307 - Cassandra crash at startup using amazon EFS as NFS
Summary: Cassandra crash at startup using amazon EFS as NFS
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Matthew Wong
QA Contact: Jianwei Hou
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-20 15:13 UTC by Brendan Mchugh
Modified: 2019-12-16 07:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-27 22:08:53 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.