accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <>
Subject [jira] [Comment Edited] (ACCUMULO-1416) FileSystemMonitor isn't necessary anymore?
Date Tue, 14 May 2013 14:55:16 GMT


John Vines edited comment on ACCUMULO-1416 at 5/14/13 2:55 PM:

Well, it wasn't the OS disk that went read only in this case.

Oh right, I can read :/

Anyway, it's an extremely nice warning/error message to have. If we can have it die on OS
disk death but error to monitor for data disk, I think that would be the best balance.
      was (Author: vines):
    Well, it wasn't the OS disk that went read only in this case
> FileSystemMonitor isn't necessary anymore?
> ------------------------------------------
>                 Key: ACCUMULO-1416
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: tserver
>            Reporter: John Vines
> With the removal of direct walogs, do we still need tservers monitoring the filesystem
and dying if things go wonky? Just had it happen and the death of the tserver didn't seem
necessary, especially with multiple disks.
> Relevant stack trace-
> {code}
> 2013-05-14 08:54:55,693 [util.FileSystemMonitor] FATAL: Exception while checking mount
points, halting process
> java.lang.Exception: Filesystem /data/04 switched to read only
>         at org.apache.accumulo.server.util.FileSystemMonitor.checkMounts(
>         at org.apache.accumulo.server.util.FileSystemMonitor$
>         at java.util.TimerThread.mainLoop(
>         at
> {code}

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message