[jira] [Commented] (ACCUMULO-84) Logger should fail into read-only mode with disk full

["Jim Zombek (Commented) (JIRA)" <ji...@apache.org>]

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

Jim Zombek commented on ACCUMULO-84:
------------------------------------

A couple of requirement questions.

1. If the Cloudbase WAL fails to log the mutation (e.g. out of disk space), the requirement is for the WAL to continue in "READ-ONLY" mode as opposed to stopping as it does now. By continuing without WAL logging,  can the Table still be recovered?

2. After the WAL enters READ-ONLY mode, is the requirement to start logging again once disk space becomes available? Or is the requirement that once the WAL enters READ-ONLY mode, it will always be in READ-ONLY mode until it is stopped and restarted?

JimZ
                
> Logger should fail into read-only mode with disk full
> -----------------------------------------------------
>
>                 Key: ACCUMULO-84
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-84
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: logger
>    Affects Versions: 1.3.5, 1.4.0, 1.5.0
>            Reporter: John Vines
>            Assignee: Eric Newton
>              Labels: failover
>             Fix For: 1.5.0
>
>
> If the disk is full for a Logger it will kill itself quickly. Instead we should have it fail into a 'read-only' mode, that way tservers can still do log recovery based on the data it has. It needs to be treated in such a way that tservers won't rely on it to log their new data, but can be used to recover older data.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira