[
https://issues.apache.org/jira/browse/ACCUMULO-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13151443#comment-13151443
]
Adam Fuchs commented on ACCUMULO-84:
------------------------------------
1. The table should not be damaged by the logger failing. The way it currently
works is that the wal write will fail, the tserver will try to find another
logger, and if no logger can be successfully written to then the write will
retry forever (I believe). This behavior should be preserved.
2. Administrator intervention to get a logger out of read only mode is fine.
This should be rare, and the failure modes of trying to recover automatically
could be complex and hard to predict. There should be a periodic notification
via the warning log that the logger is in read only mode so that we know to fix
it. This should propagate up to the monitor page.
> 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
