You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Matteo Merli (JIRA)" <ji...@apache.org> on 2012/12/21 03:37:12 UTC
[jira] [Updated] (BOOKKEEPER-524) Bookie journal filesystem gets
full after SyncThread is terminated with exception
[ https://issues.apache.org/jira/browse/BOOKKEEPER-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matteo Merli updated BOOKKEEPER-524:
------------------------------------
Attachment: 0001-BOOKKEEPER-524-Bookie-journal-filesystem-gets-full-a.patch
I'm not particularly familiar with the LedgerCache code but I think returning null should be correct when the page is not found.
> Bookie journal filesystem gets full after SyncThread is terminated with exception
> ---------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-524
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-524
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-server
> Affects Versions: 4.2.0
> Reporter: Matteo Merli
> Attachments: 0001-BOOKKEEPER-524-Bookie-journal-filesystem-gets-full-a.patch
>
>
> The SyncThread get a NPE while the rest of the bookie is still running. This causes the journal gc to be stopped and the filesystem get full.
> Tue Dec 18 17:01:18 2012: Exception in thread "SyncThread" java.lang.NullPointerException
> Tue Dec 18 17:01:18 2012: at org.apache.bookkeeper.bookie.LedgerCacheImpl.getLedgerEntryPage(LedgerCacheImpl.java:153)
> Tue Dec 18 17:01:18 2012: at org.apache.bookkeeper.bookie.LedgerCacheImpl.flushLedger(LedgerCacheImpl.java:421)
> Tue Dec 18 17:01:18 2012: at org.apache.bookkeeper.bookie.LedgerCacheImpl.flushLedger(LedgerCacheImpl.java:363)
> Tue Dec 18 17:01:18 2012: at org.apache.bookkeeper.bookie.InterleavedLedgerStorage.flush(InterleavedLedgerStorage.java:148)
> Tue Dec 18 17:01:18 2012: at org.apache.bookkeeper.bookie.Bookie$SyncThread.run(Bookie.java:221)
--
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