You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by "Eric Newton (JIRA)" <ji...@apache.org> on 2012/05/18 22:41:06 UTC

[jira] [Created] (ACCUMULO-598) write-ahead logs can leak until loggers are deleted

Eric Newton created ACCUMULO-598:
------------------------------------

             Summary: write-ahead logs can leak until loggers are deleted
                 Key: ACCUMULO-598
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-598
             Project: Accumulo
          Issue Type: Bug
          Components: logger
    Affects Versions: 1.3.6, 1.4.0
            Reporter: Eric Newton


If a tablet server doesn't close a log (because it crashed), the logger thinks it is open.  If no recover is necessary, the log will not be closed until the logger is restarted.

--
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

        

[jira] [Resolved] (ACCUMULO-598) write-ahead logs can leak until loggers are deleted

Posted by "Eric Newton (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ACCUMULO-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Newton resolved ACCUMULO-598.
----------------------------------

    Resolution: Won't Fix

No longer using independent logging servers
                
> write-ahead logs can leak until loggers are deleted
> ---------------------------------------------------
>
>                 Key: ACCUMULO-598
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-598
>             Project: Accumulo
>          Issue Type: Bug
>          Components: logger
>    Affects Versions: 1.3.6, 1.4.0
>            Reporter: Eric Newton
>
> If a tablet server doesn't close a log (because it crashed), the logger thinks it is open.  If no recover is necessary, the log will not be closed until the logger is restarted.

--
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

        

[jira] [Commented] (ACCUMULO-598) write-ahead logs can leak until loggers are deleted

Posted by "Eric Newton (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ACCUMULO-598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280161#comment-13280161 ] 

Eric Newton commented on ACCUMULO-598:
--------------------------------------

This would be fixed by the design proposed in ACCUMULO-578
                
> write-ahead logs can leak until loggers are deleted
> ---------------------------------------------------
>
>                 Key: ACCUMULO-598
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-598
>             Project: Accumulo
>          Issue Type: Bug
>          Components: logger
>    Affects Versions: 1.3.6, 1.4.0
>            Reporter: Eric Newton
>
> If a tablet server doesn't close a log (because it crashed), the logger thinks it is open.  If no recover is necessary, the log will not be closed until the logger is restarted.

--
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