You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Sijie Guo (JIRA)" <ji...@apache.org> on 2013/07/25 07:59:51 UTC

[jira] [Comment Edited] (BOOKKEEPER-604) Ledger storage can log an exception if GC happens concurrently.

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

Sijie Guo edited comment on BOOKKEEPER-604 at 7/25/13 5:58 AM:
---------------------------------------------------------------

attach a patch as what I commented here : https://issues.apache.org/jira/browse/BOOKKEEPER-604?focusedCommentId=13696005&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13696005

- obtain fileinfo before flushing
- pass fileinfo to flush
- finally release fileinfo after flush


                
      was (Author: hustlmsp):
    attach a patch 

- obtain fileinfo before flushing
- pass fileinfo to flush
- finally release fileinfo after flush


                  
> Ledger storage can log an exception if GC happens concurrently.
> ---------------------------------------------------------------
>
>                 Key: BOOKKEEPER-604
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-604
>             Project: Bookkeeper
>          Issue Type: Bug
>            Reporter: Ivan Kelly
>            Assignee: Ivan Kelly
>             Fix For: 4.2.2, 4.3.0
>
>         Attachments: 0001-BOOKKEEPER-604-Ledger-storage-can-log-an-exception-i.patch, 0001-BOOKKEEPER-604-Ledger-storage-can-log-an-exception-i.patch, 0001-BOOKKEEPER-604-Ledger-storage-can-log-an-exception-i.patch, 0001-BOOKKEEPER-604-Ledger-storage-can-log-an-exception-i.patch, BOOKKEEPER-604.diff, BOOKKEEPER-604.diff
>
>
> If a ledger is flushing, and part way through,GC kicks in, it can delete the index file before we try and flush it.

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