[CASSANDRA-13067] Integer overflows with file system size reported by Amazon Elastic File System (EFS)

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.2.11, 3.0.15, 3.11.1, 4.0-alpha1, 4.0
• Component/s: Legacy/Core

Environment

Cassandra in OpenShift running on Amazon EC2 instance with EFS mounted for data

• Severity: Normal
• Assignee: Benjamin Lerer
• Reporter: Michael Hanselmann

Authors

Benjamin Lerer

Reviewers

Alex Petrov

• Created: 21/Dec/16 15:53
• Updated: 15/May/20 07:59
• Resolved: 08/Aug/17 15:18

Description

When not explicitly configured Cassandra uses nio.FileStore.getTotalSpace to determine the total amount of available space in order to calculate the preferred commit log size. Amazon EFS instances report a filesystem size of 8 EiB when empty. getTotalSpace causes an integer overflow (JDK-8162520) and returns a negative number, resulting in a negative preferred size and causing the checked integer to throw.

Overriding commitlog_total_space_in_mb is not sufficient as DataDirectory.getAvailableSpace makes use of nio.FileStore.getUsableSpace.

AMQ-6441 is a comparable issue in ActiveMQ.

Issue Links

• is related to: CASSANDRA-13808 Integer overflows with Amazon Elastic File System (EFS)
• relates to: AMQ-6441 Incorrect File System Size Reported with Amazon Elastic File System (EFS)