cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua McKenzie (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-10957) Verify disk is readable on FileNotFound Exceptions
Date Mon, 04 Jan 2016 17:23:39 GMT


Joshua McKenzie updated CASSANDRA-10957:
    Priority: Minor  (was: Major)

> Verify disk is readable on FileNotFound Exceptions
> --------------------------------------------------
>                 Key: CASSANDRA-10957
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: T Jake Luciani
>            Priority: Minor
> In JVMStabilityInspector we only mark ourselves unstable when we get some special messages
in file not found exceptions.
> {code}
>         // Check for file handle exhaustion
>         if (t instanceof FileNotFoundException || t instanceof SocketException)
>             if (t.getMessage().contains("Too many open files"))
>                 isUnstable = true;
> {code}
> It seems like the OS might also have the same issue of too many open files but will instead
return "No such file or directory".
> It might make more sense, when we check this exception type, to try to read a known-to-exist
file to verify the disk is readable.
> This would mean creating a hidden file on startup on each data disk? other ideas?

This message was sent by Atlassian JIRA

View raw message