You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Michael Miller (JIRA)" <ji...@apache.org> on 2016/12/20 13:18:58 UTC

[jira] [Commented] (ACCUMULO-4536) Infinite loop creating empty WAL files when disk space is low

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

Michael Miller commented on ACCUMULO-4536:
------------------------------------------

Do you think this can be fixed internally in the code? Or are you thinking of just a change to default configuration values?

> Infinite loop creating empty WAL files when disk space is low
> -------------------------------------------------------------
>
>                 Key: ACCUMULO-4536
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4536
>             Project: Accumulo
>          Issue Type: Bug
>          Components: tserver
>    Affects Versions: 1.6.6
>            Reporter: Christopher Tubbs
>            Priority: Minor
>
> Saw this on 1.6.6 with a small disk for testing (32GB disk). The default walog size is around 1GB, and only 3.4GB were left available on each data node.
> The namenode reported that no data nodes had space available when trying to write the first block, so the tserver failed to write the file. It kept retrying, resulting in the namenode filling up with thousands of zero-length WAL files.
> The fix was to lower the {{tserver.walog.max.size}} to {{100M}}. Another solution would be to use a larger disk.
> The infinite loop problem, constantly creating new empty WAL files is still a problem, but it should only happen when low on disk space, which is likely going to cause other, more serious problems... and could be avoided with good system monitoring.
> I have not tested on versions newer than 1.6.6, but I imagine it's still a problem.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)