Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Tue, 14 May 2013 14:31:16 +0000 (UTC)
From: "Eric Newton (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12647506.1368540595875.316388.1368541876269@arcas>
In-Reply-To: <JIRA.12647506.1368540595875@arcas>
References: <JIRA.12647506.1368540595875@arcas>
Subject: [jira] [Commented] (ACCUMULO-1416) FileSystemMonitor isn't
 necessary anymore?
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ACCUMULO-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13657085#comment-13657085 ] 

Eric Newton commented on ACCUMULO-1416:
---------------------------------------

The monitoring is nice; but it should probably not kill itself.

                
> 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