[
https://issues.apache.org/jira/browse/ACCUMULO-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13657098#comment-13657098
]
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: https://issues.apache.org/jira/browse/ACCUMULO-1416
> 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(FileSystemMonitor.java:134)
> at
> org.apache.accumulo.server.util.FileSystemMonitor$1.run(FileSystemMonitor.java:91)
> at java.util.TimerThread.mainLoop(Timer.java:534)
> at java.util.TimerThread.run(Timer.java:484)
> {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: http://www.atlassian.com/software/jira
